feat: add focusedGuideKeys debug setting to pin a guide#879
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
@cursor review |
|
@cursor review |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
packages/react/src/modules/guide/components/Toolbar/V2/GuideHoverCard.tsx
Show resolved
Hide resolved
| <Box w="full"> | ||
| {result.error && <Box>{result.error}</Box>} | ||
| <GuideContextDetails /> | ||
| {result.error && ( |
There was a problem hiding this comment.
Unrelated, a minor style touch up.
| skipEngagementTracking: !!state.debug?.skipEngagementTracking, | ||
| ignoreDisplayInterval: !!state.debug?.ignoreDisplayInterval, | ||
| }, | ||
| debugSettings: state.debug || {}, |
There was a problem hiding this comment.
Just use the whole debug object to make life simpler.
2de17c1 to
aafdaf6
Compare
6a8548b to
d229d76
Compare
aafdaf6 to
88597c7
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #879 +/- ##
==========================================
- Coverage 67.00% 66.65% -0.36%
==========================================
Files 205 205
Lines 8948 9032 +84
Branches 1193 1201 +8
==========================================
+ Hits 5996 6020 +24
- Misses 2928 2988 +60
Partials 24 24
|

Description
focusedGuideKeysdebug setting to the guide client, an object to hold guide keys to "focus" while in debug modeforcedGuideKeydebug setting - with one difference being thatfocusedGuideKeyscan hold more than one guide keys. For now we still limit to one guide key in the toolbar UI layer, but I wanted to make this change now in case we need to come back to extend this for useGuides (i.e. force rendering multiple guides with useGuides)forcedGuideKeyafter toolbar v2 ships.Screenshots or videos
CleanShot.2026-02-26.at.16.44.00.mp4