refactor: Replace react-i18next imports with next-i18next #1844
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
next-i18n offers SSR support. Although we don't need it specifically for every component it is better to prefer it in order to maintain consistency
|
✅ Tests will run for this PR. Once they succeed it can be merged. |
ani-kalpachka
approved these changes
Jun 6, 2024
ani-kalpachka
added
the
run tests
github-actions
bot
removed
the
run tests
gparlakov
pushed a commit
to gparlakov/podkrepi-bg-frontend
that referenced
this pull request
Jun 19, 2024
…g#1844) * refactor: Replace react-i18next imports with next-i18next next-i18n offers SSR support. Although we don't need it specifically for every component it is better to prefer it in order to maintain consistency * eslint: Add rule to prevent react-i18next imports
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.
next-i18next offers SSR support. Although we don't need it specifically for every component it is better to prefer over react-i18next, in order to maintain consistency.