-
Notifications
You must be signed in to change notification settings - Fork 122
fix(cloud): redirect to tasks when initial login #3064
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
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Claude encountered an error —— View job I'll analyze this and get back to you. |
commit: |
Graphite Automations"Test" took an action on this PR • (10/03/25)1 assignee was added to this PR based on Kacper Wojciechowski's automation. |
Merge activity
|
### TL;DR Added custom error handling, 404 pages, and improved the onboarding flow with organization selection. ### What changed? - Added a custom 404 page with a "Go home" button - Created a centralized `RouteError` component for consistent error handling across routes - Added an onboarding flow with organization selection - Removed the standalone organizations index page in favor of the new onboarding flow - Enhanced the `FullscreenLoading` component to accept children - Fixed UI issues in the user dropdown by adding truncation to long usernames - Added fallback text for unknown projects and namespaces - Added Clerk task URLs for organization selection - Improved the project selection UI with better layout and styling ### How to test? 1. Test the 404 page by navigating to a non-existent route 2. Test error handling by triggering API errors 3. Test the onboarding flow by signing up as a new user 4. Verify that long usernames are properly truncated in the user dropdown 5. Check that the organization selection flow works correctly 6. Verify that the "Unknown Project" and "Unknown Namespace" fallbacks appear when appropriate ### Why make this change? These changes improve the user experience by providing better error handling and a more streamlined onboarding process. The custom 404 page and error components create a more consistent and user-friendly experience when errors occur. The new onboarding flow with organization selection makes it easier for new users to get started with the platform. UI improvements like text truncation and fallback text enhance usability and prevent layout issues.
TL;DR
Added custom error handling, 404 pages, and improved the onboarding flow with organization selection.
What changed?
RouteError
component for consistent error handling across routesFullscreenLoading
component to accept childrenHow to test?
Why make this change?
These changes improve the user experience by providing better error handling and a more streamlined onboarding process. The custom 404 page and error components create a more consistent and user-friendly experience when errors occur. The new onboarding flow with organization selection makes it easier for new users to get started with the platform. UI improvements like text truncation and fallback text enhance usability and prevent layout issues.