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
share the last loader for any new standalone components as we didn't load a new loader
Current behavior
any new component doesn't explicitly load new loader use the main app translation module
Expected behavior
any new component use the last translate loader.
What is the motivation / use case for changing the behavior?
the dialog components run out of the host component context as they are standalone, so it doesn't catch the last loaded loader.
How do you think that we should implement this?
every time we load the translateModule without create new loader use the last loaded one.
The text was updated successfully, but these errors were encountered:
ahmed-a-ibrahim
changed the title
ruse last loaded loder in standalone component which doesn't load by routes
reuse last loaded loder in standalone component which doesn't load by routes
Oct 30, 2023
share the last loader for any new standalone components as we didn't load a new loader
Current behavior
any new component doesn't explicitly load new loader use the main app translation module
Expected behavior
any new component use the last translate loader.
What is the motivation / use case for changing the behavior?
the dialog components run out of the host component context as they are standalone, so it doesn't catch the last loaded loader.
How do you think that we should implement this?
every time we load the translateModule without create new loader use the last loaded one.
The text was updated successfully, but these errors were encountered: