---
source: https://cli.eloqnt.dev/docs/lint-rules/missing-translation
docs_index: https://cli.eloqnt.dev/llms.txt
---

# missing-translation

Flags a message the source locale defines that a target locale leaves absent or empty.

## Why this is bad

A message with no translation either fails at runtime or falls back to a default, depending on how your setup handles a missing key.

## How to fix it

You can add all missing translations by running [`eloqnt translate`](https://cli.eloqnt.dev/docs/cli/translate).

This rule reports a warning instead of an error, so that you can delay adding translations while still working on a feature. By passing `--strict` to [`eloqnt lint`](https://cli.eloqnt.dev/docs/cli/lint), you can fail on warnings too (useful e.g. for [GitHub Actions](https://cli.eloqnt.dev/docs/guides/github-actions)).

## Examples

Given a source locale that defines the keys `save` and `discard`.

Examples of **incorrect** code for this rule:

```json title="messages/es.json"
{
  "discard": "Descartar"
}
```

Examples of **correct** code for this rule:

```json title="messages/es.json"
{
  "discard": "Descartar",
  "save": "Guardar"
}
```

---

For an index of every eloqnt/cli documentation page, see [https://cli.eloqnt.dev/llms.txt](https://cli.eloqnt.dev/llms.txt).
