Skip to content

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Feb 3, 2021

The return type for _getShadowRoot is actually a ShadowRoot, not a Node.

@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 Feb 3, 2021
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Feb 3, 2021
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The return type for `_getShadowRoot` is actually a `ShadowRoot`, not a `Node`.
@crisbeto crisbeto force-pushed the shadow-root-types-fix branch from caaa691 to dc26237 Compare February 3, 2021 22:01
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Feb 3, 2021
@annieyw annieyw merged commit 6fee271 into angular:master Feb 5, 2021
annieyw pushed a commit that referenced this pull request Feb 5, 2021
The return type for `_getShadowRoot` is actually a `ShadowRoot`, not a `Node`.

(cherry picked from commit 6fee271)
annieyw pushed a commit that referenced this pull request Feb 5, 2021
The return type for `_getShadowRoot` is actually a `ShadowRoot`, not a `Node`.

(cherry picked from commit 6fee271)
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Feb 8, 2021
The return type for `_getShadowRoot` is actually a `ShadowRoot`, not a `Node`.
wagnermaciel pushed a commit to wagnermaciel/components that referenced this pull request Feb 8, 2021
The return type for `_getShadowRoot` is actually a `ShadowRoot`, not a `Node`.
@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 Mar 8, 2021
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 cla: yes PR author has agreed to Google's Contributor License Agreement 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.

4 participants