LocaleAwareInterface

[earthiverse]

Feature Request

Q	A
New Feature	yes
RFC	yes
BC Break	no

Summary

laminas-i18n's Translator is now marked final (albeit softly).
We use getLocale and setLocale a lot in our projects.

We used to extend the Translator, but now that it's marked final, we can't really do that.

I'm wondering if it makes sense to have a LocaleAwareInterface with getLocale and setLocale in this base project, laminas-i18n, or if we should just roll our own interface.

[gsteel]

I think you should probably roll your own for now.

With the current workload getting other libs compatible with service manager v4, it'll be a while before attention turns to this lib and i18n.

FWIW, I wouldn't interface setLocale personally, and likely, I wouldn't use a LocaleAwareInterface either. To me, the locale is a parameter that gets passed in at the point of use, i.e. Services never "know" what the current locale is, and instead it is always passed to $service->translate($someText, $theLocale).

I can see the use-case for a service whose responsibility it is to track what the current locale is, but I'd assume that would be highly project dependent, like a routing plugin, or middleware, or possibly something in the presentation layer…