missing-key

Warning · A key of the source has no translation.

git8n check reports this rule as a warning. It fails only past --max-warnings.

Why it matters

The application shows the text of the fallback language, or the key itself, in place of the translation.

Invalid

locales/en/common.json

{
  "title": "Hello",
  "save": "Save"
}

locales/fr/common.json

{
  "title": "Bonjour"
}

$ git8n check --source en
locales/fr/common.json
  warning  common:save has no fr text.  missing-key

Read more:
  missing-key  https://git8n.sakuga.dev/docs/reference/rules/missing-key.html

0 errors, 1 warning in 2 files (en → fr, 2 keys).

Valid

locales/en/common.json

{
  "title": "Hello",
  "save": "Save"
}

locales/fr/common.json

{
  "title": "Bonjour",
  "save": "Enregistrer"
}

$ git8n check --source en
0 errors, 0 warnings in 2 files (en → fr, 2 keys).

What to do

Translate the key, in the editor or with git8n apply. If the whole file must stay untranslated in this language, mark it disabled in the manifest. --max-warnings lets a number of warnings pass.

All the rules · The command check