Nested <HotKeys/>: owner-based and parent-based contexts differ about react-hotkeys HOT 3 CLOSED

Hey @jeron-diovis.

This is expected until 0.14 lands and it's a warning you can safely ignore for now providing you're using the library as laid out in the "getting started" guide.

In 0.14 context use will be greatly simplified. https://github.com/Chrisui/react-hotkeys/blob/master/docs/getting-started.md#hotkey-map-context

If this is actually causing functional problems I'd be happy to look into it for you.

from react-hotkeys.

Shame on me, I missed this guide.
Indeed, using mixin did the trick. Thanks for pointing and for quick response.

Actually, while playing with it, I found out that nested hotkeys wasn't what I really need. I thought somehow that if I'll define a top-level HotKeys, then keyboard events, raised in it, will trigger handlers, defined in descendants. That is, I won't need to focus exact children to work with it's handlers (a kind of pubsub, actually).
Not sure it's even possible... But in practice nesting HotKeys only provides an additional abstraction layer between keycodes and business-logic's actions, nothing more.

Anyway, this lib is great. After introducing HOC it will become absolutely amazing, I think)

from react-hotkeys.

Cheers :)

I'm planning a large update which will bring up the library upto v1.0 when React v0.14 becomes stable to make the most of parent-based context and HoCs etc.

from react-hotkeys.