Configuration and time · rule
translation.field_unused
No wording in a language uses one of a message's fields.
Area 10, Configuration and time; declinable; the next step is usually the agent's.
A call gives every field a value, so a language that never writes one is either right (it needs no such word) or has forgotten a placeholder. It is a judgement call: a person answers it with a reason.
translations { order_shipped: "La commande a été expédiée."}
error: No wording of `order_shipped` writes `{name}` --> domains/shipping/translations/fr_fr.jadpo:2:5 |2 | order_shipped: "La commande a été expédiée." | ^^^^^^^^^^^^^ `{name}` is never written reason: `OrderShipped` has a field `name`, and a call gives it a value, but this language never writes it. That is right for a language that needs no such word, and it is also what a forgotten placeholder looks like. next: Write `{name}` in a wording of `order_shipped`, or remove the field, or write `decline translation.field_unused: "<why>"` above it if this is deliberate (agent) rule: translation.field_unused help: https://jadpo.dev/docs/errors/translation.field_unusedcheck failed: 1 error, 4 files
Markdown for agents: /docs/errors/translation.field_unused.md.Built from Jadpo main at a707efb.