-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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: annotate remaining base classes with @directive for ivy #17279
refactor: annotate remaining base classes with @directive for ivy #17279
Conversation
This comment has been minimized.
This comment has been minimized.
98a78e4
to
868c24b
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
868c24b
to
b9944b5
Compare
…rated Read more about this here: https://hackmd.io/vuQfavzfRG6KUCtU7oK_EA.
These base classes define class members with Angular features. Therefore they need to be decorated with `@Directive()` so that the classes can be extended in Ivy. This is an official migration that will be performed for CLI applications in version 9. angular/angular#32590.
b9944b5
to
0832020
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
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
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. |
Some base classes define class members with Angular features. Therefore
they need to be decorated with
@directive()
so that the classes can beextended in Ivy.
This is an official migration that will be performed for CLI
applications in version 9. angular/angular#32590.
Most of these classes do not cause issues yet because the removal of
ngBaseDef
has not happened yet, but it is planned.. hence the actual migration in
@angular/core
.