Add FormatJS lint rules #245
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
See: https://formatjs.io/docs/tooling/linter/ I turned on rules that seem to make sense for the default case - Enforce defaultMessage so stuff doesn't show up blank at first - Enforce description to provide context for translators - Let IDs be autogenerated as FormatJS recommends - Avoid too-complicated message variants I didn't turn on the one banning literal strings in JSX, yet, but once every message is internationalized, we could to prevent accidentally not translating something. We would want to add exceptions for deliberately untranslated things like the BikeHopper project name.
|
Part of #238 |
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.
See: https://formatjs.io/docs/tooling/linter/
I turned on rules that seem to make sense for the default case
I didn't turn on the one banning literal strings in JSX, yet, but once every message is internationalized, we could to prevent accidentally not translating something. We would want to add exceptions for deliberately untranslated things like the BikeHopper project name.