Conversation
WalkthroughAdds a Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🔇 Additional comments (1)
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 |
|
Would it also work if the whole thing had a key prop? That will clear all state, and we don't have to hunt for individual pieces. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6623 +/- ##
=======================================
Coverage 94.14% 94.15%
=======================================
Files 493 493
Lines 41080 41104 +24
Branches 4777 4783 +6
=======================================
+ Hits 38676 38700 +24
Misses 2399 2399
Partials 5 5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@PavelVanecek yes it works.. nicely, Thanks for your suggestion.. |
PavelVanecek
left a comment
There was a problem hiding this comment.
Why not key on the whole examples page? And all other pages too?
… same bug (#6637) ## Description API and Guide pages were also affected by the same bug. ## Related Issue #6618 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit ## Release Notes * **Bug Fixes** * Improved page navigation to properly reset component state when switching between pages, ensuring a fresh experience without residual data from previous pages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
GoldFoylee
left a comment
There was a problem hiding this comment.
I appreciate you taking care of this. By making sure the example component is remounted when navigating pages, the key={page} addition neatly resolves the stuck chart issue. Elegant, straightforward, and functional.
I think it looks good.
Description
Reset the example editor state whenever I navigate to a different example so the sidebar keeps working after I hit Run.
Related Issue
fixes #6618
Motivation and Context
How Has This Been Tested?
Started the docs locally, reproduced the bug, then verified the sidebar loads new examples normally after clicking Run.
Screenshots (if appropriate):
Screen.Recording.2025-11-13.at.3.mp4
Types of changes
Checklist:
Summary by CodeRabbit