Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: update to react-intl 6 #1524

Merged
merged 3 commits into from
Jun 11, 2024

Conversation

soygitana
Copy link
Contributor

@soygitana soygitana commented Jun 11, 2024

IMPORTANT:

  • Minimal set of changes to solve the problem.

Changes:

  1. react-intl lib has been upgrade to v^6.4.2

  2. BUIE has been updated to v^20.0.0

  3. deprecated addLocaleData (react-intl/locale-data has been removed from react-intl) has been removed (doc).

  4. I have to add resolution for react-intl to package.json file ( "/react-intl//@types/react": "^17.0.2"). react-intl has set @types/react to version 16 || 17 || 18 (https://github.com/formatjs/formatjs/blob/main/package.json#L61) so yarn install the latest one, however @types/react 17 i 18 are incompatible. It caused a mismatch of types in some components.


Testing:

Make sure application and strings are not broken when language is changed.


For more information, please check:

@soygitana
Copy link
Contributor Author

soygitana commented Jun 11, 2024

@jstoffan @greg-in-a-box

This is a 'duplicate' of #1509, which I accidentally closed in my fork :(. Additionally, I updated BUIE, which was blocking this PR from merging.

@soygitana soygitana marked this pull request as ready for review June 11, 2024 11:59
@soygitana soygitana requested a review from a team as a code owner June 11, 2024 11:59
@soygitana soygitana merged commit 26a073f into box:master Jun 11, 2024
3 checks passed
@soygitana soygitana deleted the MOJI-1900-react-intl-upgrade branch June 11, 2024 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants