Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reuse last loaded loder in standalone component which doesn't load by routes #1453

Open
ahmed-a-ibrahim opened this issue Oct 30, 2023 · 0 comments

Comments

@ahmed-a-ibrahim
Copy link

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.

@ahmed-a-ibrahim 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant