Summary
Define a contract format for externalizing field labels and supporting multiple languages in form definitions. Currently, labels are inline in the form contract YAML. We need a separate, localizable labels contract so forms can be rendered in different languages without duplicating the form structure.
Open questions
- File structure: one file per locale? Per API per locale?
- Fallback behavior when a translation is missing
- How label contracts are referenced from form contracts
- Plural forms and interpolation
- Relationship to the existing
labels: annotations mechanism in form contracts
Related
- #55 Contract-driven field annotations
- #81 Formalize contract schema as JSON Schema
- #94 Define form definition contract format
Moved from codeforamerica/safety-net-blueprint#131
Summary
Define a contract format for externalizing field labels and supporting multiple languages in form definitions. Currently, labels are inline in the form contract YAML. We need a separate, localizable labels contract so forms can be rendered in different languages without duplicating the form structure.
Open questions
labels: annotationsmechanism in form contractsRelated
Moved from codeforamerica/safety-net-blueprint#131