angular: migrate entity list to httpResource based service#32373
Merged
DanielFran merged 2 commits intojhipster:mainfrom Feb 21, 2026
Merged
angular: migrate entity list to httpResource based service#32373DanielFran merged 2 commits intojhipster:mainfrom
DanielFran merged 2 commits intojhipster:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request migrates Angular entity list components to use Angular's new httpResource API for a more reactive and declarative approach to HTTP request management. The changes modernize the entity list loading mechanism by replacing imperative HttpClient calls with signal-based httpResource, introduce a new utility function for controlled pluralization, and update documentation to use more semantically appropriate entity name variants.
Changes:
- Introduced a new
pluralizeutility function with aforceparameter to control pluralization behavior, allowing distinction between display names (forced plurals) and URL/file names (natural plurals) - Migrated Angular entity list services to use
httpResourcewith signal-based parameter management, replacing manual HttpClient subscription handling - Refactored service architecture to use inheritance pattern with a base plural service managing list loading and a child singular service adding CRUD operations
- Updated Java template documentation to use
entityNamePluralHumanizedinstead ofentityInstancePluralfor better semantic clarity
Reviewed changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| lib/utils/string-utils.ts | Added pluralize utility function with force parameter for controlled pluralization behavior |
| generators/spring-boot/templates/src/main/java/package/entityPackage/web/rest/_entityClass_Resource.java.ejs | Updated JavaDoc comments to use entityNamePluralHumanized for better documentation clarity |
| generators/java/generators/bootstrap/generator.ts | Updated to use new pluralize function with force parameter for relationship name pluralization |
| generators/client/entity.ts | Updated to use new pluralize function for Angular entity name pluralization |
| generators/base-application/entity.ts | Introduced force parameter in pluralization calls and updated entityNamePluralHumanized computation |
| generators/angular/templates/src/main/webapp/app/entities/entityFolder/service/entityFile.service.ts.ejs | Major refactoring to use httpResource API with signal-based parameters, introduced service inheritance pattern |
| generators/angular/templates/src/main/webapp/app/entities/entityFolder/list/entityFile.ts.ejs | Updated component to work with new httpResource-based service, removed manual HTTP subscription handling |
| generators/angular/templates/src/main/webapp/app/entities/entityFolder/list/entityFile.spec.ts.ejs | Updated tests to work with httpResource using HttpTestingController and vitest fake timers |
| generators/angular/templates/src/main/webapp/app/entities/entityFolder/list/entityFile.html.ejs | Fixed currentSearch signal invocation to use function call syntax |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
...ar/templates/src/main/webapp/app/entities/_entityFolder_/service/_entityFile_.service.ts.ejs
Outdated
Show resolved
Hide resolved
.../angular/templates/src/main/webapp/app/entities/_entityFolder_/list/_entityFile_.spec.ts.ejs
Outdated
Show resolved
Hide resolved
...ators/angular/templates/src/main/webapp/app/entities/_entityFolder_/list/_entityFile_.ts.ejs
Show resolved
Hide resolved
DanielFran
approved these changes
Feb 21, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-cilabel, you can still see CI build result at your branch.