Skip to content

Conversation

@crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 2, 2022

Most of the constructor parameters of DomPortalOutlet are only used for component portals. These changes make them optional in order to simplify the constructor. If we hit a code path that does require them, we'll throw a runtime error.

Related to the discussion in #24334.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Mar 2, 2022
@crisbeto crisbeto requested review from a team and andrewseguin as code owners March 2, 2022 12:55
@josephperrott josephperrott removed the request for review from a team March 2, 2022 18:30
Most of the constructor parameters of `DomPortalOutlet` are only used for component portals. These changes make them optional in order to simplify the constructor. If we hit a code path that does require them, we'll throw a runtime error.

Related to the discussion in angular#24334.
@crisbeto crisbeto force-pushed the 24334/portal-simplification branch from 196399d to cc455af Compare March 3, 2022 09:18
@andrewseguin andrewseguin added the action: merge The PR is ready for merge by the caretaker label Mar 24, 2022
@andrewseguin andrewseguin merged commit a4642cb into angular:master Mar 25, 2022
andrewseguin pushed a commit that referenced this pull request Mar 25, 2022
Most of the constructor parameters of `DomPortalOutlet` are only used for component portals. These changes make them optional in order to simplify the constructor. If we hit a code path that does require them, we'll throw a runtime error.

Related to the discussion in #24334.

(cherry picked from commit a4642cb)
forsti0506 pushed a commit to forsti0506/components that referenced this pull request Apr 3, 2022
…4504)

Most of the constructor parameters of `DomPortalOutlet` are only used for component portals. These changes make them optional in order to simplify the constructor. If we hit a code path that does require them, we'll throw a runtime error.

Related to the discussion in angular#24334.
@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 Apr 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants