v.5.0.0-1 #1135
JohannesKlauss
announced in
Announcements
v.5.0.0-1
#1135
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🎉 First stable Pre Release for 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.This discussion was created from the release v.5.0.0-1.
Beta Was this translation helpful? Give feedback.
All reactions