-
Notifications
You must be signed in to change notification settings - Fork 26.2k
feat(core): Add a schematics to migrate to standalone: false
.
#57643
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
Conversation
ce14dde
to
8d8674b
Compare
bcb37ba
to
dd1cd74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the reported comment about changing the exception message, this looks good.
dd1cd74
to
f5976c9
Compare
} | ||
|
||
const decoratorIdentifier = callExpression.expression; | ||
if (!ts.isIdentifier(decoratorIdentifier)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want/need this to work for import * as ng from '@angular/core'; @ng.Component()
usages?
packages/core/schematics/migrations/standalone-false/migration.ts
Outdated
Show resolved
Hide resolved
packages/core/schematics/migrations/standalone-false/migration.ts
Outdated
Show resolved
Hide resolved
f50d5da
to
83beed1
Compare
With the framework enabling `standalone` by default (making module based an opt-in), the migration will migrate none-standalone existing components and add `standalone: false` to the decorator.
83beed1
to
42fb8b9
Compare
This PR was merged into the repository by commit 6ea8e1e. The changes were merged into the following branches: main |
…lar#57643) With the framework enabling `standalone` by default (making module based an opt-in), the migration will migrate none-standalone existing components and add `standalone: false` to the decorator. PR Close angular#57643
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. |
With the framework enabling
standalone
by default (making module based an opt-in), the migration will migrate none-standalone existing components and addstandalone: false
to the decorator.The migration will also remove
standalone: true
properties as they are now not necessary anymore