-
-
Notifications
You must be signed in to change notification settings - Fork 47
fix(react-hotkeys): set hotkey options after ui commit #113 #141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
IanWorley
wants to merge
1
commit into
TanStack:main
from
IanWorley:fix-set-hotkey-options-after-ui-commit
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@tanstack/react-hotkeys': patch | ||
| --- | ||
|
|
||
| Fixed `useHotkey` updating registration options during the render phase. Options are now synced in an effect after the UI commits, so store subscribers (like `useHotkeyRegistrations`) are no longer notified mid-render, which could trigger React warnings and inconsistent state. Fixes #113. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π©Ί Stability & Availability | π‘ Minor | β‘ Quick win
π§© Analysis chain
π Script executed:
Repository: TanStack/hotkeys
Length of output: 154
π Script executed:
Repository: TanStack/hotkeys
Length of output: 10133
π Script executed:
Repository: TanStack/hotkeys
Length of output: 5254
π Script executed:
Repository: TanStack/hotkeys
Length of output: 4277
π Script executed:
Repository: TanStack/hotkeys
Length of output: 8174
π Script executed:
Repository: TanStack/hotkeys
Length of output: 6244
Move the callback sync into the commit phase.
registrationRef.current.callback = callbackmutates the hotkey manager during render, which can leak an aborted concurrent render into the active registration. TheuseEffecthere also runs after every render, andsetOptionsalways publishes a new registration map, so this still churns subscribers even when the options are unchanged. Fold both updates into the post-commit sync and skipsetOptionswhen nothing actually changed.π€ Prompt for AI Agents