[enhancement]: Refactor HotKeys Implementation

[Millu]

Is there an existing issue for this?

• I have searched the existing issues

Contact Details

No response

What should this feature add?

Hotkeys registered all over the app and they often conflict, or do two things for one hotkey

The solution is to use the react-hotkeys-hook’s scoping features to change the hotkey scope depending on where you are in the app, and enable hotkeys based on this.

Discussion notes:

We also want to centralize the key combos & associated actions and make them user-editable.

This would be implemented in stages:

1. Store the hotkey data in memory (e.g. just a constant)
2. Implement editing
   a. Persist the hotkeys to localStorage
   b. Allow editing of the hotkeys
3. Implement backend permanent storage (?)

• Are hotkeys server state or client state? I think server state, so they need to be stored in the backend, but this is open to dissenting opinions
• Needs backend storage mechanism - JSON or db?
• Needs API routes

• Upstream issue: [BUG] When multiple handlers for a single hotkey are registered, disabling one with enabled: () => false disables all later-registered handlers JohannesKlauss/react-hotkeys-hook#1035 → this is not a factor if proper scoped implementation is in place

Alternatives

No response

Aditional Content

No response

[KevinBrack]

Can you assign this to me, please?

[psychedelicious]

The react-hotkeys-hook library has a number of issues. It's not clear if it is capable enough for our needs. It looks like a theoretical v5 will improve things.