Skip to content

Conversation

jog1t
Copy link
Contributor

@jog1t jog1t commented Oct 3, 2025

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.

Copy link

vercel bot commented Oct 3, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
rivet-cloud Ready Ready Preview Comment Oct 3, 2025 9:24pm
rivet-inspector Ready Ready Preview Comment Oct 3, 2025 9:24pm
rivet-site Ready Ready Preview Comment Oct 3, 2025 9:24pm

@jog1t jog1t requested a review from NathanFlurry October 3, 2025 21:18
@jog1t jog1t marked this pull request as ready for review October 3, 2025 21:18
Copy link
Contributor Author

jog1t commented Oct 3, 2025


How to use the Graphite Merge Queue

Add 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.

Copy link

claude bot commented Oct 3, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

pkg-pr-new bot commented Oct 3, 2025

Open in StackBlitz

npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner@3064
npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner-protocol@3064

commit: 16b4477

Copy link
Contributor

graphite-app bot commented Oct 3, 2025

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.

Copy link
Contributor

graphite-app bot commented Oct 3, 2025

Merge activity

  • Oct 3, 9:20 PM UTC: jog1t added this pull request to the Graphite merge queue.
  • Oct 3, 9:21 PM UTC: CI is running for this pull request on a draft pull request (#3065) due to your merge queue CI optimization settings.
  • Oct 3, 9:22 PM UTC: Merged by the Graphite merge queue via draft PR: #3065.

graphite-app bot pushed a commit that referenced this pull request Oct 3, 2025
### 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.
@graphite-app graphite-app bot closed this Oct 3, 2025
@graphite-app graphite-app bot deleted the 10-03-fix_cloud_redirect_to_tasks_when_initial_login branch October 3, 2025 21:22
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