fix(@schematics/angular): generate services without a .service extension/type
#29869
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
…e generation The `library` schematic will now longer generate an empty Angular service with the name of the library. Using only the name would generate a file name conflict with the component now that the type suffix is no longer used by default. Additionally, services tend to be specific to a particular behavior and/or functionality and are named as such. A generically named empty service will typically be deleted or renamed.
clydin
force-pushed
the
style-guide/service-empty-type
branch
2 times, most recently
from
0e304f9 to
40a9020
Compare
clydin
added
the
action: review
…ion/type To align with the updated style guide, Angular v20 will generate services without a `.service` file extension type for all service related files by default. Projects will automatically use this naming convention. Projects can however opt-out by setting the `type` option to `Service` for the service schematic. This can be done as a default in the `angular.json` or directly on the commandline via `--type=Service` when executing `ng generate`. As an example, `example.service.ts` will now be named `example.ts`. Additionally, the TypeScript class name will be `Example` instead of the previous `ExampleService`.
clydin
force-pushed
the
style-guide/service-empty-type
branch
from
40a9020 to
f7c0f5e
Compare
alan-agius4
approved these changes
Mar 18, 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. |
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.
To align with the updated style guide, Angular v20 will generate services without a
.servicefile extension type for all service related files by default. Projects will automatically use this naming convention. Projects can however opt-out by setting thetypeoption toServicefor the service schematic. This can be done as a default in theangular.jsonor directly on the commandline via--type=Servicewhen executingng generate. As an example,example.service.tswill now be namedexample.ts. Additionally, the TypeScript class name will beExampleinstead of the previousExampleService.Fixes: #24602