Skip to content
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

build: enable coercion-types rule and fix leftover cases #17609

Merged
merged 1 commit into from
Nov 4, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Nov 4, 2019

Follow-up from #17528 that:

  • Turns on the coercion-types rule.
  • Fixes the rule not detecting abstract directives properly.
  • Fixes the rule incorrectly flagging coercion functions used inside of callbacks which are inside of setters.
  • Either fixes or works around a final set of failures.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround pr: merge safe target: major This PR is targeted for the next major release labels Nov 4, 2019
@crisbeto crisbeto added this to the 9.0.0 milestone Nov 4, 2019
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 4, 2019
@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Nov 4, 2019
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

I left out all of these since they are only for examples and my thought was that we don't want to show these in the docs. They might be rather confusing since the syntax is quite new.

LGTM if we want to go with that though.

@crisbeto
Copy link
Member Author

crisbeto commented Nov 4, 2019

I did it for the stepper example, because it shows how to extend a stepper so anybody doing it will have to do it as well. I reworked the rest since they are either internal or didn't have to coerce in the first place.

Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

Okay. Doing the custom stepper since it is advanced, sounds good to me 👍

@mmalerba mmalerba removed the action: merge The PR is ready for merge by the caretaker label Nov 4, 2019
Follow-up from angular#17528 that:
* Turns on the `coercion-types` rule.
* Fixes the rule not detecting abstract directives properly.
* Fixes the rule incorrectly flagging coercion functions used inside of callbacks which are inside of setters.
* Either fixes or works around a final set of failures.
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 4, 2019
@mmalerba mmalerba merged commit 05e6d07 into angular:master Nov 4, 2019
@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 Dec 5, 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 P2 The issue is important to a large percentage of users, with a workaround target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants