Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid elements in files #34

Open
alinkedd opened this issue Dec 17, 2023 · 0 comments
Open

Invalid elements in files #34

alinkedd opened this issue Dec 17, 2023 · 0 comments

Comments

@alinkedd
Copy link
Member

alinkedd commented Dec 17, 2023

As of now I encountered the following problems while parsing a few yml files into the tree:

  • double general.js2023.survey_intro keys in surveys file
  • double user_info.other_surveys.question keys in common file
  • Winner: t value is at wrong level in surveys file (should be shifted to the right)

upd (2023/12/31):

  • double options.top_currently_missing_from_js.static_typing keys in state_of_js file
  • double options.top_currently_missing_from_js.standard_library keys in state_of_js file
  • double options.top_currently_missing_from_js.pipe_operator keys in state_of_js file
  • double options.top_currently_missing_from_js.decorators keys in state_of_js file

upd (2024/04/01):

  • double user_info.disability_status.question keys in common file
  • double charts.freeform_data keys in results file

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant