fix(@schematics/angular): generate components without a .component extension/type
#29796
Conversation
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
clydin
force-pushed
the
style-guide/component-empty-type
branch
21 times, most recently
from
a724eab to
12110c1
Compare
…ule decorator The Angular module discovery logic previously did not check for the presence of a potential `@NgModule` decorator. This can cause false positive results for files with a module-like naming pattern.
…extension/type To align with the updated style guide, Angular v20 will generate components without a `.component` file extension type for all component related files by default. Projects will automatically use this naming convention. Projects can however opt-out by setting the `type` option to `Component` for the component schematic. This can be done as a default in the `angular.json` or directly on the commandline via `--type=Component` when executing `ng generate`. As an example, `app.component.css` will now be named `app.css`. Additionally, the TypeScript class name will be `App` instead of the previous `AppComponent`.
clydin
force-pushed
the
style-guide/component-empty-type
branch
from
12110c1 to
aae346e
Compare
alan-agius4
approved these changes
Mar 14, 2025
|
@clydin @alan-agius4 @dgp1130 as I understand it, this change only affects component-related files. Are there any plans to bring similar naming updates to other constructs like directives, pipes, or services? Would love to hear your thoughts! |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
To align with the updated style guide, Angular v20 will generate components without a
.componentfile extension type for all component related files by default. Projects will automatically use this naming convention. Projects can however opt-out by setting thetypeoption toComponentfor the component schematic. This can be done as a default in theangular.jsonor directly on the commandline via--type=Componentwhen executingng generate. As an example,app.component.csswill now be namedapp.css. Additionally, the TypeScript class name will beAppinstead of the previousAppComponent.