Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workspaces & Plans #129

Draft
wants to merge 25 commits into
base: main
Choose a base branch
from
Draft

Workspaces & Plans #129

wants to merge 25 commits into from

Conversation

raggesilver
Copy link
Owner

Let's fix our initial mistake of naming boards "workspaces." Workspaces are now what they were always supposed to be: a collection of users and boards. This is the most basic requirement for us to start working on plans — which we must implement to charge for features that actively cost money to provide (i.e file uploads).

@raggesilver raggesilver self-assigned this Oct 14, 2024
- Workspace routes /app/w
- Renamed /app/board to /app/b
- Reworked /app to show workspaces
- Introduced workspaces service and api routes
- Fixed some forms to include workspaceId
- Updated deps (fixes issue with nuxt icons timing out)
Implemented endpoints and services for creating and updating workspaces. Refactored UI to include workspace creation modal and reorganized code structure for better readability and maintainability. Introduced new constants and validation schemas for workspaces.
Implemented new general, member, and rule settings components for workspace. Integrated useQueryParam composable for tab navigation and added corresponding tabs. Updated Nuxt config to use Tailwind compatibility reset CSS.
Added a computed property to check if form data is modified before submitting. Also integrated a utility function for consistent fetch error messages across the application.
Introduce `Checkbox.vue` and `coming-soon.vue` components. Enhance workspace settings by adding descriptions and `ComingSoon` placeholders. Update form error handling to use a utility function and improve type safety in various files.
export default defineEventHandler(async (event) => {
const { user: _user } = await requireUserSession(event);

// TODO: verify if user has access to workspace
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀

@raggesilver
Copy link
Owner Author

Staging is currently broken because of this nodejs/import-in-the-middle#171 💩

We are now using MinIO for local development. This makes the set up
easier to manage & inspect, reduces the amount of .env variables we
need, and reduces the risk of accidently deleting something from
production.

We are also moving some S3-specific business logic into a service, which
should make things cleaner and easier to migrate (if we ever need to) in
the future.
This commit introduces a new Redis cache and some helper functions to
speed up caching.

Our first cached resource is the workspace usage query, which can be
very expensive (as it sums the size of every attachment on a workspace).
- Removed unused "Share board" feature from workspace page.
- Adjusted button attributes for improved consistency and style.
- Added `encodeAttachmentName` utility for safe filename encoding.
- Updated "Content-Disposition" handling for UTF-8 filenames.
- Remove useless console log in Redis utility.
- Added `onConflictDoNothing` for workspace collaborators insertion. This fixes users who accept invitations to
  workspaces they are already a part of.
- Introduced `WorkspaceMemberRow` to display individual collaborators.
- Implemented `usePublicUser` composable for fetching user data.
- Adjusted pricing page for improved collaborator limits messaging.
- Updated member settings to use `WorkspaceMemberRow` for listing users.
- Disabled animations in pricing page — they don't look good.
This bug has been plaguing me forever. We didn't insert newly created
tasks into all necessary states, which caused the edit task form to not
work properly.
Fucking nitro devs haven't fixed excessive stack depth for api return
types in over two years.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant