mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
d0a71a33b1
Notably the inheritance checking is less complete as the one in the input migration. That is because we can't efficiently determine query fields in the analyze phase of compilation units. Unless we aggresively consider every field of decorated classes as queries and complexify the merged metadata significantly, we can't reliably check for cases where a class is incompatible for migration because it overrides a member from a class that is in a different compilation unit. This is an acceptable limitation though (maybe for now), as worst case, we would migrate the class and the other compilation unit would simply break. Not ideal, but migrations are impossible to be 100% correct in general— so not a surprise. In the future, we may find ways to identify queries more reliably in analyze phase already. e.g. if the compiler were to include this metadata in the `.d.ts`, or if we decide to simply add this to the metadata, accepting potential significant HDD increase. PR Close #57854 |
||
|---|---|---|
| .. | ||
| global | ||
| primitives | ||
| reference-manifests | ||
| rxjs-interop | ||
| schematics | ||
| src | ||
| test | ||
| testing | ||
| BUILD.bazel | ||
| index.ts | ||
| package.json | ||
| PACKAGE.md | ||
| public_api.ts | ||