fix(@schematics/angular): generate services without a .service
extension/type
#29869
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
.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 thetype
option toService
for the service schematic. This can be done as a default in theangular.json
or directly on the commandline via--type=Service
when executingng generate
. As an example,example.service.ts
will now be namedexample.ts
. Additionally, the TypeScript class name will beExample
instead of the previousExampleService
.Fixes: #24602