Paul Gschwendtner ca677481a2 fix(core): undecorated-classes-with-decorated-fields migration should avoid error if base class has no value declaration (#36543) ... The undecorated-classes-with-decorated-fields migration relies on the type checker to resolve base classes of individual classes. It could happen that resolved base classes have no value declaration. e.g. if they are declared through an interface in the default types. Currently the migration will throw in such situations because it assumes that `ts.Symbol#valueDeclaration` is always present. This is not the case, but we don't get good type-checking here due to a bug in the TypeScript types. See: https://github.com/microsoft/TypeScript/issues/24706. Fixes #36522. PR Close #36543		2020-04-10 13:53:15 -07:00
..
migrations	fix(core): avoid migration error when non-existent symbol is imported (#36367)	2020-04-06 13:21:54 -07:00
test	fix(core): undecorated-classes-with-decorated-fields migration should avoid error if base class has no value declaration (#36543)	2020-04-10 13:53:15 -07:00
utils	fix(core): undecorated-classes-with-decorated-fields migration should avoid error if base class has no value declaration (#36543)	2020-04-10 13:53:15 -07:00
BUILD.bazel	build: upgrade to rules_nodejs 1.0.0 (first stable release) (#34736)	2020-01-15 14:58:07 -05:00
migrations.json	refactor(core): update missing-injectable migration description to match guide (#34125)	2019-12-02 11:21:50 -08:00
tsconfig.json	feat(core): add undecorated classes migration schematic (#31650)	2019-08-13 14:40:52 -07:00