Use i18n-tasks to audit used JS locale strings#4378
Merged
Conversation
**Why**: As a developer, I want to be warned when the locale strings in use do not match those provided by the server, so I can have confidence that the texts will be presented correctly to the user. As a developer, I want to have a well-known inventory of strings in use, so that I can have confidence in future refactoring if and how strings are being used. As a developer, I want to leverage existing tooling, so that I can feel confidence in knowing that string usage is treated consistently, and so that I don't need to deal with the overhead of maintaining a custom translation string checking utility. As a user, I want only the necessary translations to be included in the JavaScript assets, so that my pages load faster.
aduth
commented
Nov 4, 2020
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
2 participants
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.
Why:
As a developer, I want to be warned when the locale strings in use do not match those provided by the server, so I can have confidence that the texts will be presented correctly to the user.
As a developer, I want to have a well-known inventory of strings in use, so that I can have confidence in future refactoring if and how strings are being used.
As a developer, I want to leverage existing tooling, so that I can feel confidence in knowing that string usage is treated consistently, and so that I don't need to deal with the overhead of maintaining a custom translation string checking utility.
As a user, I want only the necessary translations to be included in the JavaScript assets, so that my pages load faster.