angular-docs-cn/packages/core/schematics/migrations/missing-injectable
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
..
google3 feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
BUILD.bazel fix(core): missing-injectable migration should handle forwardRef (#33286) 2019-10-25 13:26:00 -07:00
definition_collector.ts refactor(core): missing-injectable migration should respect providers of directives and components (#33011) 2019-10-14 20:24:01 +00:00
import_manager.ts feat(ivy): introduce missing-injectable migration for google3 (#30956) 2019-07-23 15:52:40 -07:00
index.ts feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
providers_evaluator.ts feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
transform.ts feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
update_recorder.ts feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00