-
Notifications
You must be signed in to change notification settings - Fork 6.8k
refactor: remove inherited coercion acceptance members #17911
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
refactor: remove inherited coercion acceptance members #17911
Conversation
Is this blocked on a new Angular release? |
@jelbourn Yes. this PR is waiting for a new Angular release since the inheritance fix just landed yesterday. |
9d6d2e3
to
6164428
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@devversion needs rebase |
ee48c0c
to
926fea2
Compare
Done. |
926fea2
to
fa9597a
Compare
@mmalerba I rebased this another time. It would be nice if we can get it in since it seems to easily need a rebase (due to a lot of golden changes) |
806fd31
to
9e05f15
Compare
Previously Angular did not inherit coercion acceptance members until we submitted an issue on the framework side. This issue will be fixed with angular/angular#34296. In preparation for that change to land, this PR removes all unnecessary acceptance members and updates the lint rule to avoid future duplications (the rule is also used to make that refactoring)
9e05f15
to
b317505
Compare
Previously Angular did not inherit coercion acceptance members until we submitted an issue on the framework side. This issue will be fixed with angular/angular#34296. In preparation for that change to land, this PR removes all unnecessary acceptance members and updates the lint rule to avoid future duplications (the rule is also used to make that refactoring) (cherry picked from commit 7a6f763)
Previously Angular did not inherit coercion acceptance members until we submitted an issue on the framework side. This issue will be fixed with angular/angular#34296. In preparation for that change to land, this PR removes all unnecessary acceptance members and updates the lint rule to avoid future duplications (the rule is also used to make that refactoring)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Previously Angular did not inherit coercion acceptance members until we submitted an issue
on the framework side. This issue will be fixed with angular/angular#34296.
In preparation for that change to land, this PR removes all unnecessary acceptance members and
updates the lint rule to avoid future duplications (the rule is also used to make that refactoring)