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
One of the configuration parameter for the TranslateModule.forRoot is the defaultLanguage parameter. Now it is a string value.
Expected behavior
Transform the defaultLanguage parameter into a provider so we can assign to it a value using for example a Factory.
What is the motivation / use case for changing the behavior?
In my application the value of the defaultLanguage is the result of a algorithm implemented by a function. Now I set the defaultLanguage in the main app component logic, but I think it's not a good practice to have initialization parameters in two different places, the main app component logic and the TranslateModule.forRoot.
Thank you.
How do you think that we should implement this?
The text was updated successfully, but these errors were encountered:
dbl81
changed the title
Configuration: defaultLanguage in TranslateModule.forRoot as a Factory
Configuration: defaultLanguage in TranslateModule.forRoot as a Provider
Mar 22, 2024
Current behavior
One of the configuration parameter for the TranslateModule.forRoot is the defaultLanguage parameter. Now it is a string value.
Expected behavior
Transform the defaultLanguage parameter into a provider so we can assign to it a value using for example a Factory.
What is the motivation / use case for changing the behavior?
In my application the value of the defaultLanguage is the result of a algorithm implemented by a function. Now I set the defaultLanguage in the main app component logic, but I think it's not a good practice to have initialization parameters in two different places, the main app component logic and the TranslateModule.forRoot.
Thank you.
How do you think that we should implement this?
The text was updated successfully, but these errors were encountered: