Lint rules
inconsistent-exact-plurals
errorFlags a translation that drops an exact plural case (e.g. =0) of the source.
Why this is bad
An exact case matches one literal number rather than a CLDR category, so the source means it for every language (e.g. an empty state for =0).
Translations can still add exact cases of their own, though. This gives translators room to word a single number differently from the rest of its category.
Examples
Given this source message:
messages/en.json
{"files": "{count, plural, =0 {No files} one {1 file} other {# files}}"}
Examples of incorrect code for this rule:
messages/es.json
{"files": "{count, plural, one {1 archivo} other {# archivos}}"}
Examples of correct code for this rule:
messages/es.json
{"files": "{count, plural, =0 {Sin archivos} one {1 archivo} other {# archivos}}"}
How to fix it
Re-translate the message for the flagged locale with eloqnt translate. Passing --id replaces the existing translation, and the post-translation checks reject any attempt that drops one of the source's exact cases.
npx eloqnt translate --id files --locale es
To fix it manually, add the exact cases of the source that the translation is missing.