fix: no-missing-keys rule reports false positive with trailing dot #394
Conversation
This file contains 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
🦋 Changeset detectedLatest commit: f578426 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
For a translation key like $t('missing.') the parse function from core utilities returns undefined.
Previously this was turned into an empty array which caused all of those paths to be false positives.
If the given key can't be parsed as "path" properly, the correct handling is to treat it as a single item path with the provided string as the only item.
This also revealed another faulty test, where keypath="'hello'" was passing even though it should not.
This was referenced Jul 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(as noted in #260 (comment))
For a translation key like
$t('missing.')the parse function from core utilities returns undefined.Previously this was turned into an empty array which caused all of those paths to be false positives.
If the given key can't be parsed as "path" properly, the correct handling is to treat it as a single item path with the provided string as the only item.
This also revealed another faulty test, where
keypath="'hello'"was passing even though it should not.