Recognize section-scoped translation keys in TranslationKeyExists - #1326
Open
VincentBorgers wants to merge 1 commit into
Open
VincentBorgers wants to merge 1 commit into
VincentBorgers wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you adding in this PR?
Fixes #721
TranslationKeyExistsreported translations from a section's schemalocalesas missing when they were referenced the way the docs describe,{{ 'sections.<section-name>.<key>' | t }}. Only the bare key was looked up in the schema.In section files the check now also strips the
sections.<section-name>.prefix and looks the rest up in the schemalocales. Bare keys work as before.What's next? Any followup issues?
#720: completions don't suggest these keys yet.
Tophatting
Ran the section from #721 through
check(): 3 offenses on 3.30.1, 0 with this change. Dawn reports the same offenses before and after.Before you deploy
changeset