Skip to content

ref(nav) rename tour to navigationTour#110387

Merged
JonasBa merged 7 commits intojb/ref/navigation/naming-navfrom
jb/ref/nav-primary-components
Mar 11, 2026
Merged

ref(nav) rename tour to navigationTour#110387
JonasBa merged 7 commits intojb/ref/navigation/naming-navfrom
jb/ref/nav-primary-components

Conversation

@JonasBa
Copy link
Member

@JonasBa JonasBa commented Mar 10, 2026

Remove stacked nav wording, rename tour to navigationTour and move the two primary nav components inside the primary folder

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Mar 10, 2026
JonasBa and others added 3 commits March 10, 2026 16:14
Fix several issues introduced by the tour/stacked nav rename:

- SVG import path was '-nav-tour.svg' (missing 'stacked-') — file was not renamed
- Tour guide key 'tour._navigation' had a leading underscore; should be 'tour.navigation'
- context.tsx used NavigationTourProvider instead of NavigationTourReminderContextProvider,
  leaving the reminder context never mounted and setShowTourReminder a no-op
- Minor: double space in comment and leading space in alt text

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@JonasBa JonasBa marked this pull request as ready for review March 11, 2026 03:19
@JonasBa JonasBa requested a review from a team as a code owner March 11, 2026 03:19
@JonasBa JonasBa requested review from a team and malwilley March 11, 2026 03:19
The tour guide key 'tour.stacked_navigation' is used as an analytics/assistant
identifier and must remain stable across refactors. The rename to 'tour.navigation'
broke the assistant mock in tests and would have silently broken analytics data.

Revert the key to its original value and add a comment to prevent future renames.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Jonas <JonasBa@users.noreply.github.com>
Copy link
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

);

return stackedNavigationTourData?.seen ?? true;
return NavigationTourData?.seen ?? true;
Copy link
Contributor

Choose a reason for hiding this comment

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

Local variable incorrectly uses PascalCase naming convention

Low Severity

The local variable NavigationTourData uses PascalCase, which in JS/TS convention is reserved for components, classes, and types. The original variable was correctly camelCase (stackedNavigationTourData), but the rename dropped the lowercase prefix, making it look like a React component. It would be navigationTourData to stay consistent with the codebase convention.

Fix in Cursor Fix in Web

Comment on lines +121 to +125
const NavigationTourData = assistantData?.find(
item => item.guide === NAVIGATION_TOUR_GUIDE_KEY
);

return stackedNavigationTourData?.seen ?? true;
return NavigationTourData?.seen ?? true;
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
const NavigationTourData = assistantData?.find(
item => item.guide === NAVIGATION_TOUR_GUIDE_KEY
);
return stackedNavigationTourData?.seen ?? true;
return NavigationTourData?.seen ?? true;
const navigationTourData = assistantData?.find(
item => item.guide === NAVIGATION_TOUR_GUIDE_KEY
);
return navigationTourData?.seen ?? true;

@JonasBa JonasBa merged commit 8d6c3fc into jb/ref/navigation/naming-nav Mar 11, 2026
53 checks passed
@JonasBa JonasBa deleted the jb/ref/nav-primary-components branch March 11, 2026 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants