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
..
google3	fix(ivy): injectable pipe schematic generating incorrect import statements (#30170)	2019-04-29 09:39:11 -07:00
BUILD.bazel	build: update rules_nodejs and clean up bazel warnings (#30370)	2019-05-14 10:08:45 -07:00
injectable_pipe_migration_spec.ts	test(core): run schematic tests with public migration collection (#30198)	2019-05-08 09:23:28 -07:00
line_mappings_spec.ts	feat(core): template-var-assignment update schematic (#29608)	2019-04-02 15:47:32 -07:00
move_document_migration_spec.ts	test(core): run schematic tests with public migration collection (#30198)	2019-05-08 09:23:28 -07:00
project_tsconfig_paths_spec.ts	refactor(core): migrations should parse cli workspace config as json5 (#30582)	2019-05-21 17:26:22 -07:00
static_queries_migration_template_spec.ts	refactor(core): static-query migration should warn about syntax failures (#30628)	2019-05-23 10:31:48 -07:00
static_queries_migration_usage_spec.ts	refactor(core): static-query migration should always use template strategy (#30628)	2019-05-23 10:31:48 -07:00
template_var_assignment_migration_spec.ts	test(core): run schematic tests with public migration collection (#30198)	2019-05-08 09:23:28 -07:00
test-migrations.json	test(core): run schematic tests with public migration collection (#30198)	2019-05-08 09:23:28 -07:00