Files

JoostK 24d1f9e87c fix(ngcc): fix undecorated child migration when exportAs is present (#34014 )

The undecorated child migration creates a synthetic decorator, which
contained `"exportAs": ["exportName"]` as obtained from the metadata of
the parent class. This is a problem, as `exportAs` needs to specified
as a comma-separated string instead of an array. This commit fixes the
bug by transforming the array of export names back to a comma-separated
string.

PR Close #34014

2019-12-09 16:13:10 -08:00

migration.ts

feat(ngcc): add a migration for undecorated child classes (#33362 )

2019-10-25 09:16:50 -07:00

missing_injectable_migration.ts

feat(ngcc): migrate services that are missing @Injectable() (#33362 )

2019-10-25 09:16:49 -07:00

README.md

feat(ivy): ngcc - support ngcc "migrations" (#31544 )

2019-07-23 21:11:40 -07:00

undecorated_child_migration.ts

feat(ngcc): add a migration for undecorated child classes (#33362 )

2019-10-25 09:16:50 -07:00

undecorated_parent_migration.ts

refactor(ngcc): rework undecorated parent migration (#33362 )

2019-10-25 09:16:50 -07:00

utils.ts

fix(ngcc): fix undecorated child migration when exportAs is present (#34014 )

2019-12-09 16:13:10 -08:00

README.md

ngcc migrations

There are some cases where source code needs to be migrated before ngtsc can compile it correctly.

For example, there are cases where ngtsc expects directives need to be explicitly attached to classes, whereas previously they were not required.

There are two ways this can happen:

in a project being developed, the code can be migrated via a CLI schematic.
in a package already published to npm, the code can be migrated as part of the ngcc compilation.

To create one of these migrations for ngcc, you should implement the Migration interface and add an instance of the class to the DecorationAnalyzer.migrations collection.

This folder is where we keep the Migration interface and the implemented migrations.

Each migration should have a unit test stored in the ../../test/migrations directory.