core
core copied to clipboard
fix(service): allow setting translations in deep objects
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.
Currently | After this PR |
|
|
This change will check if the received key has .
, creating the nested objects automatically if they do not exist in the appropriate translation object.
What is going on with this? Can anyone check it and merge it?