Optional javaabu/translatable support #10

Activity

1. n4ff4h

   added

   next-genNext-gen Javaabu packagesNext-gen Javaabu packages

   featurePackage feature from the specPackage feature from the spec

   on Nov 4, 2026
2. n4ff4h

   added a commit that references this issue on Nov 5, 2026

   Test optional javaabu/translatable support

   ...

   038e4bf
3. n4ff4h commented on Nov 5, 2026

   

   n4ff4h

   on Nov 5, 2026

   CollaboratorAuthor

   More actions

   Done, following n4ff4h/translatable#10:

   • Optional: translatable is in suggest and require-dev. It's feature-detected only in Support/Translations.
   • Storage: JSON storage (translations/lang columns on every table).
   • Models: translatable variants in Models\\Translatable are picked lazily when it's enabled and the app hasn't configured a model.
   • Seeding: Dhivehi names are seeded as the Dhivehi translation.
   • Admin forms: they get an input per language through stencil's ->translatable(), with dhivehi_name kept in step.
   • Tests: tests/Translatable covers it, and a CI leg runs without it.

   Decision: the native Dhivehi column is dhivehi_name, not name_dv, which would collide with translatable's {field}_{locale} attributes.

   Docs: docs/advanced-usage/translatable.md.
4. n4ff4h

   closed this as completedon Nov 5, 2026