6f5f481fda
Currently the undecorated-classes-with-di migration leverages NGC in order to work with metadata resolution. Since NGC by default tries to resolve referenced resources on initialization of the underlying TS program, it can result in unexpected migration failures due to missing resource files. This is especially an issue since the CLI wraps the `AngularCompilerProgram` with special logic (i.e. to support SCSS preprocessing etc.). We don't have all of this since we instantiate a vanilla NGC program. The solution to the problem is to simply treat resource requests as valid, and returning a fake content. The migration is not dependent on templates or stylesheets.. so it's the simplest and most robust solution. Fixes #32826 PR Close #32953 |
||
|---|---|---|
| .. | ||
| dynamic-queries | ||
| google3 | ||
| missing-injectable | ||
| move-document | ||
| renderer-to-renderer2 | ||
| static-queries | ||
| template-var-assignment | ||
| undecorated-classes-with-decorated-fields | ||
| undecorated-classes-with-di | ||