-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
fix(ivy): deduplicate imported module in r3_injector #27102
fix(ivy): deduplicate imported module in r3_injector #27102
Conversation
516ceeb
to
534be63
Compare
534be63
to
6dc9304
Compare
You can preview 6dc9304 at https://pr27102-6dc9304.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I would suggest is splitting this into two commits, where one implements the changes to R3Injector
and the other enables the tests.
e6098f1
to
225c659
Compare
225c659
to
4d91d18
Compare
You can preview 4d91d18 at https://pr27102-4d91d18.ngbuilds.io/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for making the changes.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The r3_injector doesn't deduplicate imported modules, meaning that you can import the same module multiple times and the providers will be overwritten everytime
What is the new behavior?
We deduplicate imports, only the first one matters like it is the case with the current renderer.
This also enables the tests from platform-server for ivy.
Does this PR introduce a breaking change?