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

applicationRef.injector vs hierarchical injector in AngularRenderer #56

Closed
Benny739 opened this issue Sep 29, 2023 · 10 comments
Closed

Comments

@Benny739
Copy link
Contributor

Hi,

is there a reason why you used the applicationRef.injector and not the passed hierarchical injector for the component in the AngularRenderer?
This way we can't pass any hierarchical injection data to the component.

@sibiraj-s
Copy link
Owner

To be honest, I don't remember why. Its been a while. I am open to better suggestions/fix.

@Benny739
Copy link
Contributor Author

I propose to switch the injector to the passed injector. This way the consumer can decide which injector to pass and take advantage of the hierarchical injector, e.g. the consumer can dynamically override providers when needed.

If you're fine with that I can create a PR.

@sibiraj-s
Copy link
Owner

Sure, Thanks. We can do that. will it be a breaking change though?

@nikes
Copy link

nikes commented Oct 18, 2023

@Benny739 what's your progress on that?

@Benny739
Copy link
Contributor Author

@sibiraj-s if someone accidentally overwrote some dependencies, it could be a breaking change, because all dependency come from the root injector atm.

@nikes the change is very small, I can test and open a PR in the next few days.

@nikes
Copy link

nikes commented Oct 18, 2023

@Benny739 Oh it would be cool to see your PR, I have some thoughts on that too, so I want to wait for your PR, maybe they will be similar =)

@sibiraj-s
Copy link
Owner

Sure.

@Benny739
Copy link
Contributor Author

PR is opened #59

@sibiraj-s
Copy link
Owner

Published in v9.1.0. Thanks @Benny739

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in the thread.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants