You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Hotkeys all seem to fail when CAPSLOCK is enabled. Unless you define both CAPS and lowercase versions of the hotkey.
Describe the solution you'd like
A simple configuration flag or boolean react property to specify if ignoreCase is true/false. By defaulting to false this could be done as a non-breaking change.
Describe alternatives you've considered
Duplicating the keyMap entry for each shortcut to provide ALLCAPS and lowercase options may seem like an obvious workaround - but this may have the side effect of listing the shortcuts twice in the Shortcut Viewer
The text was updated successfully, but these errors were encountered:
I should clarify - there's obviously still a use for Shift + 'a' and 'a' to be defined as different shortcuts. So i don't want to conflate Shift + 'a' and 'A'
Unfortunately I do not have the time to actively work on this package, but I am seeking other active maintainers. If you are willing to create a pull request or help out, that would be an excellent way of moving this forward.
Is your feature request related to a problem? Please describe.
Hotkeys all seem to fail when CAPSLOCK is enabled. Unless you define both CAPS and lowercase versions of the hotkey.
Describe the solution you'd like
A simple configuration flag or boolean react property to specify if ignoreCase is true/false. By defaulting to false this could be done as a non-breaking change.
Describe alternatives you've considered
Duplicating the keyMap entry for each shortcut to provide ALLCAPS and lowercase options may seem like an obvious workaround - but this may have the side effect of listing the shortcuts twice in the Shortcut Viewer
The text was updated successfully, but these errors were encountered: