fix(service): allow setting translations in deep objects #1382
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
|
What is going on with this? Can anyone check it and merge it? |
|
Integrated in upcoming V16 |
|
In your fork v16, please do not make people confused |
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.
This PR fixes the issue mentioned in #216 .
When we pass a key with nested properties, for example,
profilePage.header.name, it will set the key as is instead of creating the necessary nested objects.{ "profilePage.header.name": "Test" }{ "profilePage": { "header": { "name": "Test" } } }This change will check if the received key has
., creating the nested objects automatically if they do not exist in the appropriate translation object.