v1 Refactor

[chrisui]

Issue to track/discuss upcoming features/changes.

• Allow controlling parent/child mapping (in case it doesn't quite correlate with dom output - eg. imagine a contextual menu being mounted through a portal)
• Higher order component api
• Allow bubbling of event/hotkeys Allowing events to bubble #52
  • Explore "hotkey event" api as discussed in Honor event.stopPropagation #20
• Tests
• Explore possible single mousetrap/dom binding - Delegate handlers to single Mousetrap binding #2
• Expose Mousetrap reference (ie. import {Mousetrap} from 'react-hotkeys';)
• Investigate binding (inputs?) issues Event Propagation Problems #51

[chrisui]

Potentially provide first class support for initial focus state?

See: #25

[MLoughry]

@chrisui In my project, I'm already working on an HOC API wrapper around this project that I may be able to port over to this project. However, without PR #40 (or at least allowing the wrapping div to be styled), it has some issues.

The working prototype I have provides

• @registerKeyMap class decorator that takes in a keyMap argument, and wraps the class's render method in a component
• @keydownHandler method decorator that takes in a string command argument. It then wraps the class's render method with a method with a map of all decorated methods in the class.

However, I want to be sure this project is still open to development before spending effort porting my prototype to this project.

[chrisui]

Have finally (!!?!?!) kicked off this work. First priority has been getting everything updated (a lot has changed in 2 years!) and ensuring we have a robust way of testing the hotkey events so we can have good coverage. Still working on that latter part but hopefully have something to show soon!

[greena13]

Closing to track the issues individually - milestones are now being used to group issues.