-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Migration outputs in templates #58282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration outputs in templates #58282
Conversation
This build change makes it possible to share code between existing input / query migrations and output migrations.
25e66de
to
b88773a
Compare
This commits makes sure that .next usages of outputs are migrated in templates and host bindings.
b88773a
to
cda1534
Compare
packages/core/schematics/migrations/output-migration/output-migration.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/migrations/output-migration/output-migration.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/migrations/output-migration/output-migration.ts
Outdated
Show resolved
Hide resolved
caretaker note: merging this PR will require a patch from https://critique.corp.google.com/cl/688139268 (G3 BUILD files update). |
This PR was merged into the repository by commit 00e2001. The changes were merged into the following branches: main |
This commits makes sure that .next usages of outputs are migrated in templates and host bindings. PR Close #58282
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This change tracks usage of outputs in templates / host bindings. For now it replaces
.next
usage with.emit
but we might need to add more processing if needed (ex..pipe
usage - for now I'm assuming that this is not very common / not happening).