c6ecdc9a81
As of v10, undecorated classes using Angular features are no longer supported. In v10, we plan on removing the undecorated classes compatibility code in ngtsc. This means that old patterns for undecorated classes will result in compilation errors. We had a migration for this in v9 already, but it looks like the migration does not handle cases where classes uses lifecycle hooks. This is handled in the ngtsc compatibility code, and we should handle it similarly in migrations too. This has not been outlined in the migration plan initially, but an appendix has been added for v10 to the plan document. https://hackmd.io/vuQfavzfRG6KUCtU7oK_EA?both. Note: The migration is unable to determine whether a given undecorated class that only defines `ngOnDestroy` is a directive or an actual service. This means that in some cases the migration cannot do more than adding a TODO and printing an failure. Certainly there are more ways to determine the type of such classes, but it would involve metadata and NgModule analysis. This is out of scope for this migration. PR Close #36921 |
||
|---|---|---|
| .. | ||
| dynamic-queries | ||
| google3 | ||
| missing-injectable | ||
| module-with-providers | ||
| move-document | ||
| renderer-to-renderer2 | ||
| static-queries | ||
| template-var-assignment | ||
| undecorated-classes-with-decorated-fields | ||
| undecorated-classes-with-di | ||