4.3.0

Feature

• Allows output null (#134) 2cd2a96

4.2.4

Fix

• Fix TextArea DOM ref when specifying textAreaComponent (#133) de230ad

Chore

• Run Prettier in pre-commit hook (#130) 508636a

4.2.3

Fix

• Improve autocomplete positioning (Fixes #124) (#127) 8310e0a by @andypearson
• Never decrease index in listener (#126) 625c61f by @JelteF
• Fix prop-types peerDep version (#123) 26423b9 by @O4epegb

Thanks to all contributors! 👏

4.2.2

Fix

• This fix edge bug when you move to the other token by arrows (#122) 7a213c7

4.2.1

Fix

• Let's close the autocomple once selection is made (#121) 6aaae38

4.2.0

Feature

• Allow custom components to be used instead of standard <textarea/> (#113) 1819328 1fec924

Fix

• Fixed behavior, when autocomplete, doesn't show up in some cases (#119) d795251
• Remove unnecessary Escape key listener (#118) a37def3

Chore

• chore: bump the webpack-dev-server because of CVE-2018-14732 bb68d8d

4.1.0

Fix

• fix correct event propagation (#114) 2294bdb
• boundariesElement supports dynamic dimensions (#115) 3f822ab

(Breaking change 💣 I've completely removed closeOnClickOutside prop because it can't be combined together with the new behavior of events. Also, I think it should be like that as default. Sorry for semver inconsistency. )

4.0.0

Hey everyone! Happy holidays 🎅! Today, we've prepared a new major release for us full of nice things, give it a spin and send us feedback!

Features 🚀

• new autocomplete behavior (#107) a9c2577
• autocomplete auto-position based on boundariesElement (#111) f30dab7 (Finally, after ~1 year 💪 )

Breaking changes 💣

New autocomplete behavior (#107) changed the way how the autocomplete works. It behaves in a more natural way, I hope.

I've completely removed closeOnClickOutside (#114) prop because it can't be combined together with the new behavior of events. Also, I think it should be like that as default.

Chore

I've updated the most dependenices in the project. Babel 7, Webpack 4, Cypress 3,..

Also, you've might see, there are currently no issues. I'd like to say that I'm planning to move this package into maintaining phase. So more likely I'm not gonna extend the scope of this library anymore and I'll be focusing to fixing bugs mostly. But still if you get some nice idea, just create an issue and we'll see.

The future...

I got also an idea of how it would be possible to change the API, because the current one is kinda limiting due to bounding to textarea element. It would be much better to use a system of so-called drivers and thus support React Native for example. I'm thinking about this a lot, but this would require a complete rewrite. The codebase got kinda messy because the API grew with the requirements so there is some debt. Unfortunately, I did some not really fortuned decisions in the past and some part of the codebase suffers form it, that's also the reason for "no more features" mode. It's barely possible now. However, I'm truly happy where we got in a year and a half. I hope this library solved some issue for you! If so, don't hesitate to create issue / PR with your project – I will intercorporate it into the Readme. Thanks. 🤝

- Jakub "jukben" Benes

3.1.5

Fix

• Controlled value should trigger autocomplete as well (#110) 5b82861

Chore

• Update deps (#108) 8afb0dc

3.1.4

Fix

⚠️ This version fixes serious performance issue, thanks for noticing @guidogast! The upgrade is recommended.

• fixed output function performance (#106) c209192