v5.5.1

Fix

Fixed select not working on React 18 / Testing Library React 13 (@bramdevries)

v5.5.0

New feature

This reverts the previous change (https://github.com/romgain/react-select-event/releases/tag/v5.4.0).
See #90 for details

v5.4.0

New feature

The react-select container is now dynamically selected using react-select's css class names where possible (@th3fallen)

v5.3.0

New feature

The select method now accepts any valid dom-testing-library TextMatch objects (eg. string, regex, function, number) as the optionOrOptions parameter. (@lpproulx)

v5.2.0

New Feature

The container option can now be a function if the container needs to be lazily evaluated.

v5.1.0

New Feature

All actions are now wrapped in React’s act.

v5.0.0

Breaking Change

• Removed the autoSelect option to the create function introduced in v4.2.0. (@fgs-dbudwin)

New Feature

• Added a new waitForElement option to the create function, replacing autoSelect. This should be used in cases when creating a new option fails. (@fgs-dbudwin)

Note The breaking change won't affect users who didn't upgrade to v4.2.0 to use the autoSelect option. Since v4.2.0 had only been released for less than two days when v5.0.0 was published, that should hopefully be transparent for most people.

v4.2.0

New Feature

• Added a config option to control whether a new option should be selected after creation (defaults to true, which is the current behavior)
  This is useful in cases when the creation of the new option depends on services that may fail. (@fgs-dbudwin)

See issue #35 for more details.

v4.1.4

Bugfix

• Fixed an issue where select wouldn't work on already-selected options

v4.1.3

Bugfixes

• Fixed an issue where select didn't work properly when using custom option labels.