feat(@schematics/angular): add update migration to keep previous style guide generation behavior#30050
Merged
Merged
Conversation
angular-robot
Bot
added
detected: feature
clydin
changed the title
clydin
force-pushed
the
style-guide/migration
branch
from
c969852 to
fe5d0e6
Compare
clydin
added
the
action: review
…e guide generation behavior
When updating to Angular v20 via `ng update`, a migration will be executed
that will add schematic generation (`ng generate`) defaults to the workspace.
These defaults will ensure that existing projects will continue to generate
files as done in previous versions of the Angular CLI. All new projects (via `ng new`) or
projects that do not explicitly contain these options in their workspace
will use the updated style guide naming behavior.
The option values for the `schematics` field are as follows:
```
{
'@schematics/angular:component': { type: 'component' },
'@schematics/angular:directive': { type: 'directive' },
'@schematics/angular:service': { type: 'service' },
'@schematics/angular:guard': { typeSeparator: '.' },
'@schematics/angular:interceptor': { typeSeparator: '.' },
'@schematics/angular:module': { typeSeparator: '.' },
'@schematics/angular:pipe': { typeSeparator: '.' },
'@schematics/angular:resolver': { typeSeparator: '.' },
}
```
clydin
force-pushed
the
style-guide/migration
branch
from
fe5d0e6 to
2337300
Compare
alan-agius4
approved these changes
Apr 8, 2025
alan-agius4
added
action: merge
|
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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When updating to Angular v20 via
ng update, a migration will be executed that will add schematic generation (ng generate) defaults to the workspace. These defaults will ensure that existing projects will continue to generate files as done in previous versions of the Angular CLI. All new projects (viang new) or projects that do not explicitly contain these options in their workspace will use the updated style guide naming behavior.The option values for the
schematicsfield are as follows: