You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do have quite nested translation objects in different files, i.e.:
{ "generic": { "hello": "world" } }
and
{ "generic": { "foo": "bar" } }
In the current version, only "foo.bar" is available as angular.extend is used. It extends the translation object on the first level, so "generic" is replaced in this case.
Which drawbacks would angular.extend have? If it's backwards compatibility, one could fall back to angular.merge if angular.extend is not available.
The text was updated successfully, but these errors were encountered:
Hi all,
I do have quite nested translation objects in different files, i.e.:
{ "generic": { "hello": "world" } }
and
{ "generic": { "foo": "bar" } }
In the current version, only "foo.bar" is available as
angular.extend
is used. It extends the translation object on the first level, so "generic" is replaced in this case.Which drawbacks would
angular.extend
have? If it's backwards compatibility, one could fall back toangular.merge
ifangular.extend
is not available.The text was updated successfully, but these errors were encountered: