Warn about invalid translations
See original GitHub issuebroken:
n-comments: '{numComments, plural, =1 {1 comment} andere {# comments}}'
fixed:
n-comments: '{numComments, plural, =1 {1 comment} other {# comments}}'
it would have been cool if ember-intl
could’ve warned me about the broken plural rule. instead sentry.io was reporting “infinite rendering invalidations” and apparently the user interface for the users using that translation was repeated several times (see https://github.com/skylines-project/skylines/issues/615).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Warn about invalid translation keys with TS #1195
Provide stricter TS typing based on the provided schema types, so that invalid keys would be prevented/warned in type checks (editor, build, etc)....
Read more >Why warn about invalid utf-8 in commments? : r/cpp
It's a potential readability issue. Invalid UTF-8 most often mean malformed characters in comments meaning you just seeing garbage instead of ...
Read more >Translations and invalid arguments of type resource | Vazcell
We access the route on our server /web/sites/default/files/translations and we confirm that both the owner/group and the access to the folder is allowed...
Read more >1006063 – RFE: Enforcing validation for translation update
The stat on the document should be updated. Message 1 and 3 are saved as translated. Message 3 are shown as invalid. The...
Read more >Translation template is invalid (wp-content) | WordPress.org
Occured after unstalled 2.4.5 version. Strings such as tags autor (metadata ones) are not translated now… The page I need help with: [log...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll have to think about it. Might be a good idea, yeah. What I’m a little worried about is having a mismatch between the CLDR versions and not being able to resolve
cldr-core
properly.Woohoo 😃
Do you think it’s worth pulling this work into a stand-alone addon, when you’re ready, into something like
ember-intl-icu-linter
? This can be a future task, just bike shedding on how we can scale this to add additional linting (i.e., key collision detection).