All Versions
12
Latest Version
Avg Release Cycle
83 days
Latest Release
2060 days ago

Changelog History
Page 1

  • v1.2.0-beta.3 Changes

    August 30, 2018
    • 👍 [feature] Add code support by @gforge
    • 🗄 [deprecate] keyCode prop in favour of code by @gforge
    • [feature] Allows for keyValue, code and keyCode to come in array format by @gforge
    • [breaking] No longer add a <div /> wrapper around the KeyHandler component, but use React.Fragment instead

  • v1.2.0-beta.2 Changes

    August 21, 2018
    • 🛠 [bugfix] Pass original props to component we are decorating when using one of the decorators

  • v1.2.0-beta.1 Changes

    August 21, 2018
    • [feature] Use rollup to bundle up the code

  • v1.1.0 Changes

    July 31, 2018

    ⚡️ > There's two major bugs in 1.1.0, it is highly recommended to update to 1.2.0 or downgrade to 1.0.1

    • 👍 [feature] Add flow support by @gforge
    • 🛠 [bugfix] Fallback from event.keyCode to event.which for browsers such as FireFox when using the keypress event name. @gforge

  • v1.0.1 Changes

    October 26, 2017
    • 👍 [feature] Loosen react dependency to support React 16

  • v1.0.0 Changes

    August 28, 2017
    • 👍 [breaking] Drop keyName support
    • 🛠 [bugfix] Get rid of deprecation warnings

  • v0.3.0 Changes

    September 13, 2016
    • [feature] Treat content editable elements as inputs by @jamesfzhang. This means the key handle will be ignored for events triggered from these elements. (Draft.js support)

  • v0.2.0 Changes

    April 17, 2016
    • [feature] Loosen react dependency for future react versions
    • 🗄 [deprecate] keyName prop in favour of keyValue
    • [feature] Added prop types
    • 👍 [feature] Add support for W3C KeyboardEvent.key by @leocavalcante

  • v0.1.0 Changes

    March 02, 2016
    • [feature] Add decorators
    • [feature] Ignore key events from form elements
    • [feature] Key names

  • v0.0.4 Changes

    February 27, 2016
    • 🛠 [bugfix] Use right function to remove the event listener