Support for nested JSON about ngx-translate-extract HOT 7 CLOSED

Closed via 7822916

from ngx-translate-extract.

I'm not sure this can be implemented.

How would we tell the difference between PAGES.SHARED.MeetingNotFound which we want nested and STRING.WITH.DOTS which we wouldn't want nested?

Personally I'm using english strings as keys in my projects, which could easily confuse any JSON nesting logic.

from ngx-translate-extract.

Could it be implemented with a switch? In a large project it will be really difficult to manage all the keys if they are at the same level. A switch which treats DOT(.) as nested structure would be idle and the default functionality could be as it is today. what do you think about that?

from ngx-translate-extract.

Supporting nested JSON means way more complex code to handle merging of strings and we would have to introduce a CLI argument that only applies to JSON format, making the tool more complicated to use, understand and maintain.

You can use the dot structure you do now in combination with the just added --sort argument to sort keys alphabetically. That way your translations are still grouped in the translation file. Personally I think that's Good Enough™.

Alternatively you could write a custom script to post process your translations to convert dot keys to nested JSON.

from ngx-translate-extract.

I'm going to keep this issue open while I think about other options.

from ngx-translate-extract.

I think we could add a new format/compiler. A NestedJsonCompiler that flattens strings on parse and unflattens on compile.

Used via ng2-translate-extract ... --format=nested-json

from ngx-translate-extract.

Thanks, that would be good.

from ngx-translate-extract.