Skip to content

Releases: JohannesKlauss/react-hotkeys-hook

v4.6.1

02 Nov 09:54
Compare
Choose a tag to compare

What's Changed

  • Consider custom element when checking if event is by @HJK181 in #1164
  • Bump http-proxy-middleware from 2.0.6 to 2.0.7 in /documentation by @dependabot in #1217
  • Bump express from 4.19.2 to 4.21.0 in /documentation by @dependabot in #1210

New Contributors

Full Changelog: v4.6.0...v4.6.1

v4.6.0

02 Nov 09:45
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.5.1...v4.6.0

v4.5.1

02 Sep 09:58
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.5.0...v4.5.1

v.5.0.0-1

09 Feb 10:32
Compare
Choose a tag to compare
v.5.0.0-1 Pre-release
Pre-release

🎉 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 the HotkeysProvider has been renamed to activeScopes
  • If all scopes are disabled in the HotkeysProvider no hotkeys will be active

useHotkeys

  • The hook now only listens to the code of the hotkey, not the produced key. This will get rid of all the confusion between different keyboard layouts, multiple accidental triggers and so on.
  • Special character mappings to the german keyboard layout code have been removed
  • The splitKey option has been renamed to delimiter
  • The combinationKey option has been renamed to delimiter
  • New Option 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

  • Fixed a bug where listening to control instead of ctrl wouldn't trigger correctly

Migration Guide

  • If you are using the splitKey option, rename that to delimiter
  • If you are using the combinationKey option, rename that to splitKey

If you are listening to special characters like shift+1 in order to listen for the exclamation mark, rewrite your hook like so:

useHotkeys('!', callback, {useKey: true})

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:

useHotkeys('shift+1', callback)

useKey defaults to false, 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 and z. On a german layout those keys are swapped. So to comply with every possible keyboard layout, you would set useKey: true to listen to the produced key.

useHotkeys('y', callback, {useKey: true}) // Triggers if the user hits their y key on the keyboard depending on the layout
useHotkeys('y', callback) // Triggers if the user hits the y key implying US keyboard layout

v4.5.0

06 Feb 14:41
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.4.4...v4.5.0

v4.4.4

12 Jan 13:25
Compare
Choose a tag to compare

What's Changed

  • Fix several shortcuts not triggering anymore. #1110
  • chore(deps): update dependency @types/react to v18.2.47 by @renovate in #1113
  • fix(deps): update dependency react-hotkeys-hook to v4.4.3 by @renovate in #1114

Full Changelog: v4.4.3...v4.4.4

v4.4.3

04 Jan 10:03
6f2c199
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.4.2...v4.4.3

v4.4.2

04 Jan 09:44
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.4.1...v4.4.2

v4.4.1

04 Jul 07:44
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.4.0...v4.4.1

v4.4.0

14 Apr 14:38
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v4.3.8...v4.4.0