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
If I do not want to set the Variantfor each TemplateInstance then the only way I could find to set it seems to be via TemplateLocator.
But usually I'm fine with how and from where templates are loaded, so implementing a TemplateLocator for this seems like overkill.
So it would be nice to have some way to configure which locale (and charset) is used.
Implementation ideas
Maybe extend (and rename?) quarkus.qute.content-types so that you can also specify locale and encoding?
Or just introduce quarkus.qute.locale and .encoding?
The text was updated successfully, but these errors were encountered:
Maybe extend (and rename?) quarkus.qute.content-types so that you can also specify locale and encoding?
We could start with quarkus.qute.default-locale and quarkus.qute.default-encoding. Although for encoding I'd encourage users to stay with the default - UTF-8.
- honor quarkus.default-locale and introduce
quarkus.qute.default-charset
- also fail the build if a localized interface does not extend a message
bundle interface
- resolvesquarkusio#21405
Description
If I do not want to set the
Variant
for eachTemplateInstance
then the only way I could find to set it seems to be viaTemplateLocator
.But usually I'm fine with how and from where templates are loaded, so implementing a
TemplateLocator
for this seems like overkill.So it would be nice to have some way to configure which locale (and charset) is used.
Implementation ideas
Maybe extend (and rename?)
quarkus.qute.content-types
so that you can also specify locale and encoding?Or just introduce
quarkus.qute.locale
and.encoding
?The text was updated successfully, but these errors were encountered: