Current behavior

Currently, most notably with the recent changes. There's no way to get translations for another language without having to change the current language.

Expected behavior

Even though it might not always be used, there's no reason to block the functionality of translating other languages other than the currently selected language.

What is the motivation / use case for changing the behavior?

We at Group Claes adopted the deprecated @groupclaes/ngx-translate-router project from Gilsdav. We're updating the plugin to handle SSR and especially SSG routes. Currently there's no exposed way to load translations on the server-side to generate and translate the routes for languages other than the current language.

How do you think that we should implement this?

Provide overloads to read based on the key and language for translateservice.instant or translateservice.get