Ayrton

Happy to add support however I do not use React native, so I don't really have an idea where to get started

Firing the key handler for each component is the expected behaviour, if this is unwanted you should move the `KeyHandler` up one (or more) level(s) and pass the necessary props...

@gforge that seems a separate issue, could you create a separate issue? @vkolova I am not sure I understand how/why can you explain please

What happens when the `keyEventName` is set to `keypress': ```jsx ```

@princed completely agree, this needs to be 1:1, @leocavalcante started amazing work on this #10, see also the original issue #7.

@princed started working on this in #17 let's continue the conversation there :)

@villesau I'm open to improvements, what is it you want to achieve with this?

@villesau I think I like that - ideally the library would be able to let the user handle the event handling but also have a baked in version of handling...

@meandavejustice #17 makes sure you can expect the same event behaviour in this library as in react. It doesn't add support for multiple key codes. #91 is adding support to...

This feels like this can be the same possible solution that @villesau would like (described in https://github.com/ayrton/react-key-handler/issues/4#issuecomment-233568602). As mentioned in that issue I'm open to improvements and more than happy...