We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TranslationKeyExists
Describe the bug When using the locales object in a section schema, Theme Check incorrectly flags them as missing
locales
Source
// section/test-section.liquid <p>{{ 'sections.test-section.title' | t }}</p> <p>{{ 'sections.test-section.description.desktop' | t }}</p> <p>{{ 'sections.test-section.description.mobile' | t }}</p> {% schema %} { "name": "Section", "locales": { "en": { "title": "Title", "description": { "desktop": "Lorem ipsum dolor sit amet consectetur, adipisicing elit.", "mobile": "Lorem ipsum dolor sit amet" } } } } {% endschema %}
Expected behaviour No errors
Actual behaviour The first three lines all have TranslationKeyExists errors
Debugging information
The text was updated successfully, but these errors were encountered:
Good catch. Seems like the auto-completion also ignores in-file translations.
Sorry, something went wrong.
Ah looks like you already reported that too ❤ #720
No branches or pull requests
Describe the bug
When using the
locales
object in a section schema, Theme Check incorrectly flags them as missingSource
Expected behaviour
No errors
Actual behaviour
The first three lines all have
TranslationKeyExists
errorsDebugging information
The text was updated successfully, but these errors were encountered: