angular-cn/packages/core/schematics/test/google3
Paul Gschwendtner 4d23b60d09 fix(core): missing-injectable migration should not migrate providers with "useExisting" (#33286)
We should not migrate the reference from `useExisting`. This is because
developers can only use the `useExisting` value as a token. e.g.

```ts
@NgModule({
  providers: [
    {provide: AppRippleConfig, useValue: rippleOptions},
    {provide: MAT_RIPPLE_OPTIONS, useExisting: AppRippleConfig},
  ]
})
export class AppModule {}
```

In the case above, nothing should be decorated with `@Injectable`. The
`AppRippleConfig` class is just used as a token for injection.

PR Close #33286
2019-10-25 13:26:00 -07: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 fix(core): missing-injectable migration should not migrate providers with "useExisting" (#33286) 2019-10-25 13:26:00 -07: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