Closed beck closed 9 years ago
@stefanor - your thoughts?
Pro: The source json committed to the repo is valid json. No modification is needed to the serialization process. Our tagging mechanism can evolve without making edits to gigantic json files.
FYI, @imorrison
We need to look at some site.json files and try to generate include/exclude patterns for some harder to reach keys. We also need to consider the nastiness of the markup generated by text widget usage in our site.json files. That may be prohibitive, but we won't know until we look.
So, does that config mean that it translates both description
s in
{
"foo": {
"description": "Foo",
"bar": {
"description": "Foo - Bar",
},
},
}
Yes.
Seems simple enough. :+1:
Problem & Goals
Solution
Message extraction and translation injection be done via task configuration.
An idea cooked up with @thomasw - the task configuration will have a list of object keys to include & exclude when performing extraction/translation.
Example, if this is the json:
with config:
Then we'll get the following extracted:
Pros/Cons