Skip to content
This repository was archived by the owner on Jun 17, 2025. It is now read-only.

Conversation

xballoy
Copy link
Contributor

@xballoy xballoy commented Jun 5, 2020

Bump react-select to latest version.

I followed the migration guide.
The only change for us is the new import for the async react-select component.

@guillaume-chervet @samuel-gomez @youf-olivier

@youf-olivier
Copy link
Contributor

No breaking change on the R3 of react-select ?

@xballoy
Copy link
Contributor Author

xballoy commented Jun 5, 2020

The breaking changes are:

  • Upgrade from Emotion 9 to Emotion 10 → we don't use it
  • UMD builds deprecated → we don't use it
  • React 16.8 required as peer dependencies → done with build: required React 16.8.0 as peer dependency #620
  • Normalized Values #3416 → on removal of all selected values in an isMulti Select, the value passed to onChange is null and not []

The last point is the only one that could be a breaking change for us.

youf-olivier
youf-olivier previously approved these changes Jun 5, 2020
@youf-olivier
Copy link
Contributor

Can you add a Breaking change info in the commit message ?

https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#heading=h.gbbngquhe0qa

BREAKING CHANGE: on removal of all selected values in an isMulti
MultiSelect, the value passed to onChange is null and not [].
@xballoy
Copy link
Contributor Author

xballoy commented Jun 5, 2020

I added a breaking change

@xballoy xballoy requested a review from youf-olivier June 5, 2020 14:58
@youf-olivier youf-olivier merged commit b42cff8 into AxaFrance:master Jun 18, 2020
@xballoy xballoy deleted the feature/bumpReactSelect branch June 18, 2020 08:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants