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

feat(fe2): Create/Join Workspace as part of signup flow #3997

Open
wants to merge 45 commits into
base: main
Choose a base branch
from

Conversation

andrewwallacespeckle
Copy link
Contributor

@andrewwallacespeckle andrewwallacespeckle commented Feb 17, 2025

You will need the following frontend feature flags:
FF_WORKSPACES_NEW_PLANS_ENABLED=true
FF_FORCE_WORKSPACE_MEMBERSHIP=true

image image image image

@andrewwallacespeckle andrewwallacespeckle changed the title feat(fe2): Everything is a workspace feat(fe2): Create/Join Workspace as part of signup flow Feb 19, 2025
Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

@Mikehrn
Copy link
Contributor

Mikehrn commented Feb 21, 2025

After I verify my email, I get the "verify additional email" screen (even with a new account), but something gets stuck in a loop until it just crashed everything. Is this only on my machine? I cant repro this on another branch 🤔

Screenshot 2025-02-21 at 20 46 23
Screen.Recording.2025-02-21.at.20.47.19.mov

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

Copy link
Contributor

📸 Preview service has generated an image.

})

const allWorkspaces = computed(() => {
const requested = (
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason why items in and status: request.status is needed? Could be something like this:

const allWorkspaces = computed(() => [
  ...workspaceJoinRequests.value.items.map(request => ({ ...request.workspace })),
  ...discoverableWorkspaces.value.map(workspace => ({ ...workspace, status: 'Request to join' }))
])

Also not sure about using 'Request to join' as a status, I guess because you render the status in the button but I wouldn't mix them as its not really a status

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The request.status is needed because DiscoverableList_Requests returns workspace data nested under a request object with status, but DiscoverableList_Discoverable returns workspace data directly, so we need to preserve the status when combining them. Does that make sense or maybe I'm misunderstanding?

I fixed the second part

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.

2 participants