-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Description
As of now I encountered the following problems while parsing a few yml files into the tree:
doublegeneral.js2023.survey_introkeys insurveysfile- double
user_info.other_surveys.questionkeys incommonfile Winner:t value is at wrong level insurveysfile (should be shifted to the right)
upd (2023/12/31):
- double
options.top_currently_missing_from_js.static_typingkeys instate_of_jsfile - double
options.top_currently_missing_from_js.standard_librarykeys instate_of_jsfile - double
options.top_currently_missing_from_js.pipe_operatorkeys instate_of_jsfile - double
options.top_currently_missing_from_js.decoratorskeys instate_of_jsfile
upd (2024/04/01):
doubleuser_info.disability_status.questionkeys incommonfiledoublecharts.freeform_datakeys inresultsfile
I believe these should be fixed to make the files valid in terms of translations.
These are not problems at yml level, but they are important in our case, as we need unique keys and Winner: may be parsed as another command/node rather than text.
There may be more of these as I will continue translating using my tool for syncing with base files.
Metadata
Metadata
Assignees
Labels
No labels