Adds i18Next support to React #290
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oicramps
changed the base branch from
development
to
feature/react-typescript
oicramps
changed the base branch from
feature/react-typescript
to
development
|
@oicramps We have some conflicts here. Other than that, is this good to go? |
I'll solve the conflicts later today, and then we are good to go. I'll let you know when the PR is ready to merge |
|
@idmarjr I've solved the conflicts |
ArthurMota9
approved these changes
Dec 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Configures
react-i18nextto handle internationalization in the react codebaseDepends on: Typescript support to React #289