Implement key press functionality from a user perspective

[juanca]

What: Implement user interaction of pressing a single key with some modifiers

Why: This is especially useful for testing accessibility interactions (keyboard interactions) on UI elements.

How:

• Interaction is solely on the active element because a user will always be on some element
• Any key is "pressable" given the key name
• The 4 popular modifiers (alt, ctrl, meta, shift) are implemented and fired around the pressed key
  • Looks like there might be more key to implement but I think we can work on these in the future

Checklist:

• Documentation
• Tests
• Typings
• Ready to be merged
  

Closes #354

A couple of notes:

• The event is always fired on the active element since a user will always perform an interaction on the active element
• Event which key is not implement because it is deprecated
• Event code / keyCode key is not implement because it can vary on type of key (KeyA, Digit1, AltLeft, etc), opting for a more simple interface

[codecov]

Codecov Report

Merging #371 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #371   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           12        13    +1     
  Lines          376       390   +14     
  Branches       109       118    +9     
=========================================
+ Hits           376       390   +14     

Impacted Files	Coverage Δ
src/index.js	100.00% <ø> (ø)
src/key-press.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f4eae9c...d0d3d96. Read the comment docs.

[juanca]

I can whip up documentation if we're okay with this new API.

I am not sure what to do with typings. Is there some work I need for that particular checklist item?

[kentcdodds]

I'd prefer this functionality be built in via the type utility. So: type(input, '{ArrowDown})...

[nickmccurdy]

For reference: #354

[juanca]

I started digging into this and I think I discovered unplanned features:

I am thinking the PR will add support for navigation keys. It's pretty simple if I am only concerned about keyboard navigation for accessibility (simple keydown + keyup). However, it gets more complex: the type method involves managing the value and cursor/selection state in various elements; the navigation keys also have a side effect of changing the cursors or selection range.

I'll give it another go on Friday.