Update dependency react-select to v4 - autoclosed #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.1.0
->4.3.1
Release Notes
JedWatson/react-select
v4.3.1
Compare Source
Patch Changes
v4.3.0
Compare Source
Minor Changes
focusedOption
is now passed to the MenuList Component as a propPatch Changes
menuShouldScrollIntoView=false
Documentation Updates
v4.2.1
Compare Source
Patch Changes
v4.2.0
Compare Source
Minor Changes
2ffed9c6 #4444 Thanks @Rall3n! - Use accessor props to get value and label in
compareOption
2baf5a9d #4414 Thanks @ebonow! - Add
ariaLiveMessages
prop for internationalization and other customizations, addaria-live
prop, and other accessibility fixes. Inspired heavily from the work done by @Kashkovsky, @radegran, @Malgalad, and @TheHollidayInn - thanks to them, @bozdoz for the thorough testing and recommendations, and for everyone who contributed constructive feedback towards a better accessibility experience.7cdb8a6b #4391 Thanks @ebonow! - Pass and sanitize CommonProps passed to Group and Input components
Patch Changes
c955415c #4437 Thanks @ebonow! - Set event listeners to be non-passive to remove Chrome console warnings
3ca22b2f #3827 Thanks @mitchellhamilton! - Memoize stripDiacritics in createFilter for the input with memoize-one so that stripDiacritics is not called for the same string as many times as there are options every time the input changes
Inspired by https://blog.johnnyreilly.com/2019/04/react-select-with-less-typing-lag.html
dce3863f #4423 Thanks @Methuselah96! - Remove browser alias fields in order to fix SSR apps
ec7c0728 #4443 Thanks @ebonow! - Allow tabIndex prop Type to be number or string
v4.1.0
Compare Source
Minor Changes
b5f9b0c5 #4342 Thanks @Methuselah96! - Standardized innerProps and className props on customizable components
19b76342 #3911 Thanks @eugenet8k! - Add
removedValues
toonChange
event meta when the action isclear
(when the user clears the value in the Select)Patch Changes
f600d13f #4422 Thanks @Methuselah96! - Fix finding focusable options for groups
a016c878 #4420 Thanks @Methuselah96! - Bump dependency on @babel/runtime in order to fix compatibility issues with Webpack 5
10b5f5a5 #4404 Thanks @Methuselah96! - Remove unnecessary dependency on @emotion/css
v4.0.2
Compare Source
Patch Changes
v4.0.1
Compare Source
Patch Changes
v4.0.0
Compare Source
Upgrade Guide
Summary
onChange
(Modify onChange with empty value behaviour for multi select to always pass an empty array JedWatson/react-select#4339) - theonChange
handler is now always passed an array of options ifisMulti
is set totrue
NonceProvider
componentDetails
Standardize value passed to
onChange
This change makes it so that the first parameter passed to the
onChange
callback will now always be an array of options ifisMulti
is set totrue
and will always be a single option ornull
ifisMulti
is set tofalse
. Previously the first parameter ofonChange
could be an array ornull
whenisMulti
was set totrue
.That means if you were previously using nullish coalescing in order to handle
null
forisMulti
:You can now remove the nullish coalescing because
onChange
will always be an array whenisMulti
is set totrue
:Emotion 11
The
NonceProvider
component now requires acacheKey
prop that corresponds to the newly requiredkey
prop for the Emotion cache. This won't affect you if you aren't usingNonceProvider
. See #4283 for more details.Remove usage of UNSAFE React methods
This isn't necessarily a breaking change, but it required a large refactor in order to accomplish so we released this in a major upgrade in case it has some unintended consequences.
Changelog
Major Changes
02050675 #4339 Thanks @Methuselah96! - Standardized value passed to onChange
26b6325c #4283 Thanks @majgaard! - Upgrades Emotion dependency to v11.0.0
BREAKING CHANGE: The NonceProvider component now requires a
cacheKey
prop that corresponds to thekey
for the Emotion cache.b2488bb5 #4313 Thanks @Methuselah96! - Removed usages of UNSAFE React methods
Patch Changes
v3.2.0
Compare Source
Minor Changes
c615e93d #4084 Thanks @JedWatson! - Changed the
cx
andgetValue
props that are passed to components into instance properties, which means they now pass a referential equality check on subsequent renders.This is helpful, for example, when you're optimising the performance of rendering custom Option components - see #3055
72f6036f #4306 Thanks @bladey! - Remove duplicate prop createOptionPosition
Patch Changes
ee638d46 #4275 Thanks @Methuselah96! - Adds react ^17.0.0 to peer dependencies for React 17 support
a0133f19 #4154 Thanks @brenshanny! - Creatable: Fixed removing MultiValues that have identical values. See issue #4137 for details.
d1e660c6 #4213 Thanks @eythort! - Added a guard to the
ScrollCaptor
component to check thatel
exists before callingremoveEventListener
, fixes intermittent errorsa1e1db25 #4373 Thanks @Methuselah96! - Fixed value passed to onChange when clearing value
2ad29d61 #4136 Thanks @Methuselah96! - Base aria-live message on tabSelectsValue prop
ad890f27 #4326 Thanks @Methuselah96! - Updated react-input-autosize to v3.0.0
b28d9922 #3990 Thanks @nikitaindik! - Fixed onCreateOption is not always called for Creatable
24ba8702 #4289 Thanks @slimklim! - Added
innerProps
prop to the built-inMenuList
component to reduce the need for additional DOM nodes or forking internal code when passing additional props to the DOM element the MenuList component is rendering.See issue #4265 for an explanation.
v3.1.1
Compare Source
Patch Changes
c8d74bd5 #3979 Thanks @mitchellhamilton! - Fix repository field
c8447f48 #4034 Thanks @sophiebits! - Improve performance of option filtering when ignoreAccents is enabled (the default)
7af1aafb #4295 Thanks @JedWatson! - Fix menuplacement context
32ad5c04 #3892 Thanks @flexdinesh! - Fix react-select ignoring HTML5 "form" attribute
6af14fbb #3897 Thanks @lorisdev! - Removes the call to
onMenuOpen
on every input changeIf you were relying on this undesired behavior it may be a breaking change.
Please upgrade accordingly.
0eb1ef96 Thanks @JedWatson! - Fixes touch issues in IE11
ad608c8f #3928 Thanks @dpordomingo! - Update MenuPlacer context usage in order to the new React Context API
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.