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

..

injectable-pipe

build: update rules_nodejs and clean up bazel warnings (#30370)

2019-05-14 10:08:45 -07:00

move-document

fix(core): migrations not always migrating all files (#30269)

2019-05-08 11:54:33 -07:00

static-queries

refactor(core): static-query migration should warn about syntax failures (#30628)

2019-05-23 10:31:48 -07:00

template-var-assignment

build: update rules_nodejs and clean up bazel warnings (#30370)

2019-05-14 10:08:45 -07:00