Skip to content

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

Closed
wants to merge 2 commits into from

Conversation

JeanMeche
Copy link
Member

@JeanMeche JeanMeche commented Sep 3, 2024

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.

The migration will also remove standalone: true properties as they are now not necessary anymore

@angular-robot angular-robot bot added detected: feature PR contains a feature commit area: core Issues related to the framework runtime labels Sep 3, 2024
@ngbot ngbot bot added this to the Backlog milestone Sep 3, 2024
@JeanMeche JeanMeche force-pushed the feat/standalone-false branch from ce14dde to 8d8674b Compare September 3, 2024 16:56
@JeanMeche JeanMeche marked this pull request as ready for review September 3, 2024 16:56
@JeanMeche JeanMeche force-pushed the feat/standalone-false branch 2 times, most recently from bcb37ba to dd1cd74 Compare September 3, 2024 17:03
Copy link
Contributor

@thePunderWoman thePunderWoman left a 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.

@JeanMeche JeanMeche force-pushed the feat/standalone-false branch from dd1cd74 to f5976c9 Compare September 4, 2024 10:02
}

const decoratorIdentifier = callExpression.expression;
if (!ts.isIdentifier(decoratorIdentifier)) {
Copy link
Member

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?

@pullapprove pullapprove bot requested a review from atscott September 4, 2024 15:57
@JeanMeche JeanMeche force-pushed the feat/standalone-false branch 6 times, most recently from f50d5da to 83beed1 Compare September 5, 2024 17:42
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.
@JeanMeche JeanMeche force-pushed the feat/standalone-false branch from 83beed1 to 42fb8b9 Compare September 5, 2024 17:50
@AndrewKushnir AndrewKushnir added the target: major This PR is targeted for the next major release label Sep 6, 2024
@AndrewKushnir AndrewKushnir added the action: presubmit The PR is in need of a google3 presubmit label Sep 6, 2024
@AndrewKushnir
Copy link
Contributor

Presubmit.

@AndrewKushnir AndrewKushnir added action: merge The PR is ready for merge by the caretaker and removed action: presubmit The PR is in need of a google3 presubmit labels Sep 6, 2024
@thePunderWoman
Copy link
Contributor

This PR was merged into the repository by commit 6ea8e1e.

The changes were merged into the following branches: main

and-oli pushed a commit to and-oli/angular that referenced this pull request Sep 30, 2024
…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
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime detected: feature PR contains a feature commit target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants