angular-docs-cn/packages/core/schematics/test/google3
Paul Gschwendtner 15fefdbb8d feat(core): missing-injectable migration should migrate empty object literal providers (#33709)
In View Engine, providers which neither used `useValue`, `useClass`,
`useFactory` or `useExisting`, were interpreted differently.

e.g.

```
{provide: X} -> {provide: X, useValue: undefined}, // this is how it works in View Engine
{provide: X} -> {provide: X, useClass: X}, // this is how it works in Ivy
```

The missing-injectable migration should migrate such providers to the
explicit `useValue` provider. This ensures that there is no unexpected
behavioral change when updating to v9.

PR Close #33709
2019-11-18 15:47:20 -08:00
..
BUILD.bazel test(core): cleanup bazel target names for schematic tests (#32318) 2019-08-28 17:11:04 -07:00
dynamic_queries_spec.ts feat(core): add dynamic queries schematic (#32231) 2019-09-11 19:14:03 -04:00
explicit_query_timing_rule_spec.ts test(core): remove "enableIvy" compiler option from migration tests (#32954) 2019-10-02 14:53:41 -07:00
missing_injectable_rule_spec.ts feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
no_template_variable_assignment_rule_spec.ts test(core): remove "enableIvy" compiler option from migration tests (#32954) 2019-10-02 14:53:41 -07:00
renderer_to_renderer2_spec.ts test(core): remove "enableIvy" compiler option from migration tests (#32954) 2019-10-02 14:53:41 -07:00
undecorated_classes_with_decorated_fields_spec.ts test: clean up explicit dynamic query usages (#33015) 2019-10-17 16:10:10 -04:00