Add back i18next-parser-config #10
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
Open
fredericrous
reviewed
Mar 8, 2024
| @@ -0,0 +1,112 @@ | |||
| // i18next-parser.config.js | |||
|
|
|||
| export default { | |||
There was a problem hiding this comment.
I think it would be simpler to replace this file by just what we are using and let the defaults not mentioned. It is also safer to do so because you get less breaking changes over time if the package maintainers introduce breaking changes on config properties @rperon
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.
i18next parser config got deleted when upgrading. It is now back and can be used with the command:
> npx i18nextTest Plan
Checklist
Screenshots