angular-cn/integration/ng_update_migrations/src
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
..
app feat(core): missing-injectable migration should migrate empty object literal providers (#33709) 2019-11-18 15:47:20 -08:00
assets build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
environments build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
favicon.ico build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
index.html build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
main.ts build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
polyfills.ts build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
styles.less build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00
test.ts build: create integration test for ng-update migrations (#32349) 2019-08-29 12:34:43 -07:00