Paul Gschwendtner 132c61dfd4 refactor(core): static-query migration should warn about syntax failures (#30628) ... Currently if a project has source-files with syntax failures and the migration has been started on a broken project, we silently migrate *as much as possible*, but never notify the developer that the project was in a broken state and that he can re-run the migration after the failures are fixed. Additionally the template strategy does not need to exit gracefully if it detects Angular semantic diagnostics on generated files (template type checking). These diagnostics are not relevant for the query timing analysis. PR Close #30628		2019-05-23 10:31:48 -07:00
..
template_strategy	refactor(core): static-query migration should warn about syntax failures (#30628)	2019-05-23 10:31:48 -07:00
test_strategy	fix(core): static-query migration should gracefully exit if AOT compiler throws (#30269)	2019-05-08 11:54:33 -07:00
usage_strategy	fix(core): static-query usage migration strategy should detect ambiguous query usage (#30215)	2019-05-09 14:39:06 -07:00
timing-strategy.ts	fix(core): static-query migration should gracefully exit if AOT compiler throws (#30269)	2019-05-08 11:54:33 -07:00