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>enabledScopesin theHotkeysProviderhas been renamed toactiveScopesHotkeysProviderno hotkeys will be activeuseHotkeyssplitKeyoption has been renamed todelimitercombinationKeyoption has been renamed todelimiteruseKey: Setting this to true will listen to the produced key rather than the code. Helpful if you want to listen to something like?,+,!...🐛 Bugfixes
controlinstead ofctrlwouldn't trigger correctlyMigration Guide
splitKeyoption, rename that todelimitercombinationKeyoption, rename that tosplitKeyIf you are listening to special characters like
shift+1in 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:useKeydefaults 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
yandz. On a german layout those keys are swapped. So to comply with every possible keyboard layout, you would setuseKey: trueto 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