Add keySeparator configuration option #729
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
|
@all-contributors please add @testerez for code |
|
I've put up a pull request to add @testerez! 🎉 |
|
@testerez I pre-released under 1.3.0-canary.2. Thanks for your contribution. |
|
Thanks for the quick review! |
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.
keySeparatorfalseto disable keys nesting in JSON translation files. Can be useful if you want to use natural text as keys.string|false'.'Use case: I'd like to be able to use natural text as keys. This improves the developer experience because I don't have to come-up with a key for each of my texts. Also, I'm using
i18next-parserso I don't even have to touch translation files most of the time.For info, i18next offers a similar option: https://www.i18next.com/overview/configuration-options