You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optional support using javaabu/translatable's contract for other packages: in suggest, feature-detected, documented on its own page, and tested with and without it.
Done: settings declared ->translatable() get one input per locale when javaabu/translatable is enabled. WidgetForm implements stencil's ResolvesTranslatableFields, so no model trait is needed. They're stored as locale => value and rendered in the current locale, falling back to the default. Translatable is in suggest, detected only through Support\Translations, and documented in docs/advanced-usage/translatable-settings.md. Tested with it (TranslatableWidgetsTest) and without it (the CI leg). Decision: as in stencil's contract, the primary (required) language is the editor's current locale; the other languages are optional.
Activity
Optional translatable widget settings, Dhivehi translations
n4ff4h commentedon Nov 5, 2026
Done: settings declared
->translatable()get one input per locale when javaabu/translatable is enabled.WidgetFormimplements stencil'sResolvesTranslatableFields, so no model trait is needed. They're stored aslocale => valueand rendered in the current locale, falling back to the default. Translatable is insuggest, detected only throughSupport\Translations, and documented indocs/advanced-usage/translatable-settings.md. Tested with it (TranslatableWidgetsTest) and without it (the CI leg). Decision: as in stencil's contract, the primary (required) language is the editor's current locale; the other languages are optional.