Skip to content

Conversation

@JeanMeche
Copy link
Member

Before this fix, a self import would define the component twice in the directiveRegistry which would then fire a NG0300 when compiled with the JIT.

fixes #50525
Note: #50554 also fixes #50525, there were two issues in one.

  • Bugfix

Does this PR introduce a breaking change?

  • No

Before this fix, a self import would define the component twice in the `directiveRegistry` which would then fire a `NG0300` when compiled with the JIT.

fixes angular#50525
@JeanMeche JeanMeche force-pushed the fix/standalone-nested-imports branch from ed04c12 to 9b1b396 Compare June 2, 2023 21:03
@JeanMeche
Copy link
Member Author

Duplicate with #50559

@JeanMeche JeanMeche closed this Jun 2, 2023
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 3, 2023
@JeanMeche JeanMeche deleted the fix/standalone-nested-imports branch July 12, 2023 08:08
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug (or Docs Bug?): Unable to test recursive standalone component due to NG0300

1 participant