Skip to content

refactor: add support for noImplicitAny #13381

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
Oct 5, 2018

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Oct 1, 2018

Enables the noImplicitAny compiler option and fixes all of the resulting compiler errors.

Fixes #13330.

@crisbeto crisbeto added the target: major This PR is targeted for the next major release label Oct 1, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 1, 2018
@crisbeto crisbeto force-pushed the 13330/no-implicit-any branch 3 times, most recently from 9092bd8 to 0b5bc38 Compare October 1, 2018 21:25
@Inject(DIALOG_REF) private dialogRefConstructor,
@Inject(DIALOG_SCROLL_STRATEGY) private _scrollStrategy,
@Inject(DIALOG_REF) private dialogRefConstructor: Type<DialogRef<any>>,
@Inject(DIALOG_SCROLL_STRATEGY) scrollStrategy: any,
Copy link
Member

Choose a reason for hiding this comment

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

Why can't this be ScrollStrategy?

(same for other places that inject a strategy)

Copy link
Member Author

Choose a reason for hiding this comment

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

It's actually a () => ScrollStrategy. It can't have the actual type in here, because the compiler complains about it. I tried introducing a new type called ScrollStrategyFactory, but that ended up breaking in a different way.

Copy link
Member

Choose a reason for hiding this comment

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

Could you add a TODO to change it back once we're using the ivy renderer? It will fix the problem that prevents the correct type from being used.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done.

@crisbeto crisbeto force-pushed the 13330/no-implicit-any branch 2 times, most recently from b4ab821 to 5251a42 Compare October 3, 2018 18:53
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

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 3, 2018
@jelbourn jelbourn changed the title feat: add support for noImplicitAny refactor: add support for noImplicitAny Oct 3, 2018
@jelbourn jelbourn added the merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed label Oct 3, 2018
Enables the `noImplicitAny` compiler option and fixes all of the resulting compiler errors.

Fixes angular#13330.
@crisbeto crisbeto force-pushed the 13330/no-implicit-any branch from 5251a42 to eb3dc7e Compare October 5, 2018 05:55
@vivian-hu-zz vivian-hu-zz merged commit b8c1024 into angular:master Oct 5, 2018
roboshoes pushed a commit to roboshoes/material2 that referenced this pull request Oct 23, 2018
Enables the `noImplicitAny` compiler option and fixes all of the resulting compiler errors.

Fixes angular#13330.
@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 9, 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 merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable --noImplicitAny for library code
5 participants