164d160b22
Currently the `static-query` migrations fails at the final step of updating a query when the query already specifies options which cannot be transformed easily. e.g. the options are computed through a function call: `@ViewChild(..., getQueryOpts());` or `@ViewChild(..., myOptionsVar)`. In these cases we technically could add additionally logic to update the query options, but given that this is an edge-case and it's potentially over-engineering the migration schematic, we just always add a TODO for the timing and print out the determined query timing in the console. The developer in that case just needs to manually update the logic for the query options to contain the printed query timing. Potentially related to: https://github.com/angular/angular-cli/issues/14298 PR Close #30178 |
||
|---|---|---|
| .. | ||
| google3 | ||
| BUILD.bazel | ||
| injectable_pipe_migration_spec.ts | ||
| line_mappings_spec.ts | ||
| move_document_migration_spec.ts | ||
| project_tsconfig_paths_spec.ts | ||
| static_queries_migration_template_spec.ts | ||
| static_queries_migration_usage_spec.ts | ||
| template_var_assignment_migration_spec.ts | ||