Skip to content

refactor: avoid casting document to any in constructor #10775

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

Merged
merged 1 commit into from
Apr 10, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 9, 2018

Removes all the places where we were casting the Document to any when passing it in to the constructor, in order to avoid AoT compilation issues. It seems like this is no longer necessary as of 6.0.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 9, 2018
@crisbeto crisbeto force-pushed the document-constructor-any branch from 9b00f73 to a7fd539 Compare April 9, 2018 18:24
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@josephperrott josephperrott added pr: lgtm action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful and removed pr: needs review labels Apr 9, 2018
@tinayuangao
Copy link
Contributor

@crisbeto please fix the lint errors

Removes all the places where we were casting the `Document` to `any` when passing it in to the constructor, in order to avoid AoT compilation issues. It seems like this is no longer necessary as of 6.0.
@crisbeto crisbeto force-pushed the document-constructor-any branch from a7fd539 to 132a468 Compare April 10, 2018 05:17
@crisbeto
Copy link
Member Author

I'm not seeing any lint errors @tinayuangao. I've rebased it just in case.

@tinayuangao tinayuangao merged commit e60f5fc into angular:master Apr 10, 2018
jelbourn added a commit to jelbourn/components that referenced this pull request Apr 12, 2018
tinayuangao pushed a commit that referenced this pull request Apr 12, 2018
@Kiramuxa
Copy link

I do not see coerceCssPixelValue in export?

@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 Sep 8, 2019
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 P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants