Is your request related to a problem? Please describe.
Currently VIntl can only be initialised globally, or manually, but without benefits of plugin. I think this is kind of a bummer, especially if you want to have things like localised routes.
Describe the solution you'd like
I think it would be nice if VIntl separated controller into two or three things: loader/cache (loads all locales and holds the messages), scope (takes in loader's messages, maybe extends them (?), and instantiates IntlShape for them), consumer (just an accessor to scope).
Describe alternatives you've considered
- Initialising VIntl manually takes effort, and there are many nuances not really a way to share states between instances (?).
Additional context
N/A
Is your request related to a problem? Please describe.
Currently VIntl can only be initialised globally, or manually, but without benefits of plugin. I think this is kind of a bummer, especially if you want to have things like localised routes.
Describe the solution you'd like
I think it would be nice if VIntl separated controller into two or three things: loader/cache (loads all locales and holds the messages), scope (takes in loader's messages, maybe extends them (?), and instantiates IntlShape for them), consumer (just an accessor to scope).
Describe alternatives you've considered
Additional context
N/A