fix: onboarding bounce rate#942
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | b56fe7f | May 14 2026, 07:27 AM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | b56fe7f | Commit Preview URL | May 14 2026, 07:28 AM |
How to use the Graphite Merge QueueAdd the label Main 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 finished @MaheshtheDev's task in 1m 13s —— View job Reviewing PR #942
SummaryThis PR adds a catch-all route ( No issues found — clean implementation that correctly uses Next.js server-side redirect with no risk of infinite loops or breaking existing routes. Score: 10/10 |
There was a problem hiding this comment.
Overview: Adds a catch-all route to redirect invalid onboarding sub-paths (e.g., /onboarding/step1, /onboarding/foo) back to /onboarding.
Issues found: None — this looks good to ship.
The implementation is clean:
- Uses Next.js
redirect()correctly (server-side redirect) - No infinite redirect risk since
/onboardingroutes to the main page, not the catch-all - No existing sub-routes under
/onboardingthat would be broken by this change - API routes under
/api/onboarding/*are unaffected
Score: 10/10
No description provided.