fix(onboarding): run the tour in the project you just created - #8277
fix(onboarding): run the tour in the project you just created#8277talissoncosta wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Docker builds report
|
✅ private-cloud · depot-ubuntu-latest-arm-16 — run #19273 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
🗂️ Previous results✅ private-cloud · depot-ubuntu-latest-16 — run #19273 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
✅ oss · depot-ubuntu-latest-arm-16 — run #19273 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
✅ oss · depot-ubuntu-latest-16 — run #19273 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)Details
✅ private-cloud · depot-ubuntu-latest-arm-16 — run #19269 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)Details
✅ private-cloud · depot-ubuntu-latest-16 — run #19269 (attempt 1)Playwright Test Results (private-cloud - depot-ubuntu-latest-16)Details
✅ oss · depot-ubuntu-latest-arm-16 — run #19269 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-arm-16)Details
✅ oss · depot-ubuntu-latest-16 — run #19269 (attempt 1)Playwright Test Results (oss - depot-ubuntu-latest-16)Details
|
Visual Regression19 screenshots compared. See report for details. |
ensureProject took whichever project the API returned first, so a returning user's tour could act on a project they never onboarded in, and an empty one would be seeded with a flag that isn't theirs. Take the newest project instead. Creating a project and clicking Getting Started is how you run onboarding again, and #8217's rule still decides whether that project may be toured at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ff125a9 to
5e15af2
Compare
docs/if required so people know about the feature.Changes
Stacked on #8217, which decides whether a project may be toured. This decides which project we look at.
ensureProjecttook whichever project the API returned first, so onboarding couldn't be re-run by creating a project, and an empty first project got seeded instead. Now it takes the newest.Still open: if that newest project is a colleague's and still empty, it's still seeded. Telling that apart needs a persisted "has onboarded" flag on the user.
How did you test this code?
test:unit(407) andlintclean, no typecheck errors in the touched files