Jadpo is experimental and not ready for production. These docs follow the compiler's main branch as of 5 Nov 2026. What's built · Install 0.3.0

ReferenceErrors

Errors Configuration · rule

`translation.locales_required`

Translations without declared locales.

Area 10, Configuration; not declinable; the next step is usually the agent's.

Each language file is for one of the locales the application supports, and each supported locale words every message. With no locales { } there is nothing to check the wording against.

example

translations {    order_shipped: "Your order for {name} has shipped."}

jadpo checkcheck failed: 1 error, 3 files

error Translations need the application's locales

--> domains/shipping/translations/en_gb.jadpo:1:1

  |1 | translations {  | ^^^^^^^^^^^^ no locales declared

reason: Each language file is for one of the locales the application supports, and each supported locale words every message. None is declared, so there is nothing to check the wording against.
next: Declare them in app.jadpo, for instance locales { default: Locale.en_gb supported: [Locale.en_gb] } (agent)
rule: translation.locales_required
help: https://jadpo.dev/docs/errors/translation.locales_required

Markdown for agents: /docs/errors/translation.locales_required.md.Built from Jadpo main at aee2e8f.