cli.translations_arguments
A jadpo translations command names no action, one it doesn't have, or a locale the project doesn't translate into.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo translations lists what is left to translate, records the wording each translation was made from, and exchanges it with a translation service. Accepting a locale's wording is a person's decision about one locale, so it needs to know which.
What it looks like
A project that supports only its default locale, asked to accept French:
jadpo translations accept fr error fr isn't a locale with translations
- reason
- This project supports no locale besides its default, which is what the others are translated from.
- next
- Add a locale to
supported:inlocales { }(agent) - rule
- cli.
translations_ arguments - help
- https://jadpo.
dev/docs/errors/cli. translations_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
An action it doesn't have is refused with the ones it does:
jadpo translations sync error sync isn't something jadpo translations does
- reason
jadpo translationscanmissing,unused,update,accept,builtin,exportorimport.- next
- Run
jadpo translations missingto see what is left to translate (agent) - rule
- cli.
translations_ arguments - help
- https://jadpo.
dev/docs/errors/cli. translations_ arguments
How to fix it
If the app should be translated into French, add it to supported: in locales { }, then accept its wording:
jadpo translations accept frIt records the wording each French message was made from.
Related
Markdown for agents: /docs/errors/cli.translations_arguments.md.Built from Jadpo main at aee2e8f.