-
-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Update dependency react-hotkeys-hook to v5 - autoclosed #7391
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
👍 @renovate[bot] Thank you for raising your pull request and contributing to our Community |
TestGru AssignmentSummary
Tip You can |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7391 +/- ##
=======================================
Coverage 88.27% 88.27%
=======================================
Files 825 825
Lines 60707 60707
Branches 4027 4027
=======================================
Hits 53591 53591
Misses 7116 7116
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
90befa7
to
ecccda8
Compare
ecccda8
to
4b1ccf7
Compare
⏳ Processing in progress |
This PR contains the following updates:
^4.6.2
->^5.0.0
Release Notes
JohannesKlauss/react-keymap-hook (react-hotkeys-hook)
v5.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: JohannesKlauss/react-hotkeys-hook@v5.0.2...v5.1.0
v5.0.1
Compare Source
v5.0.0
Compare Source
🎉 Version 5!
Most users should not need to do any migration, but for those who use special characters (+,-/$? and so on) or a different delimiter key than
+
there is a bit of work to do.🚨 Breaking Changes
<HotkeysProvider>
enabledScopes
in theHotkeysProvider
has been renamed toactiveScopes
HotkeysProvider
no hotkeys will be activeuseHotkeys
splitKey
option has been renamed todelimiter
combinationKey
option has been renamed todelimiter
useKey
: Setting this to true will listen to the produced key rather than the code. Helpful if you want to listen to something like?
,+
,!
...🐛 Bugfixes
control
instead ofctrl
wouldn't trigger correctlyMigration Guide
splitKey
option, rename that todelimiter
combinationKey
option, rename that tosplitKey
If you are listening to special characters like
shift+1
in order to listen for the exclamation mark, rewrite your hook like so:This will listen to the produced key instead of the code. Listening for shift is not necessary anymore, because the hook will only check if the produced key matches
!
, no matter how it has been produced. This will be layout agnostic.If you want to listen to specifically
shift+1
, then use the hotkey like this:useKey
defaults tofalse
, so you only need to set it, if you want to listen to special characters.One common use case for this is listening to
y
andz
. On a german layout those keys are swapped. So to comply with every possible keyboard layout, you would setuseKey: true
to listen to the produced key.New Contributors
Full Changelog: JohannesKlauss/react-hotkeys-hook@v4.6.2...v5.0.0
Configuration
📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.