NEW Add rule to catch malformed _t() calls #12
Merged
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
GuySartorelli
force-pushed
the
pulls/1/i18n-rule
branch
from
ae50f5a to
c5d433a
Compare
GuySartorelli
force-pushed
the
pulls/1/i18n-rule
branch
2 times, most recently
from
7c9c388 to
0c46fd4
Compare
GuySartorelli
force-pushed
the
pulls/1/i18n-rule
branch
from
0c46fd4 to
d5819ee
Compare
emteknetnz
requested changes
Aug 6, 2024
emteknetnz
approved these changes
Aug 6, 2024
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.
This should catch cases where keys in calls to
_t()(either globally or viai18n::_t()directly) are malformed. It'll also catch some cases where the text collector wouldn't be able to correctly evaluate the key.Issue