inconsistent-exact-plurals

Why this is bad

An exact case matches one literal number rather than a CLDR category, so it answers to the source rather than to the locale (e.g. to implement empty states).

Examples

Given the source message "{count, plural, =0 {No files} one {1 file} other {# files}}".

Examples of incorrect code for this rule:

{
  "files": "{count, plural, one {1 archivo} other {# archivos}}"
}

Examples of correct code for this rule:

{
  "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 whose exact cases differ from the source.

npx eloqnt translate --id files --locale es

To fix it manually, add or remove exact cases until they match the source’s.