align Angular User Management UI with standard entity templates#32359
Open
DhairyasheelS wants to merge 7 commits intojhipster:mainfrom
Open
align Angular User Management UI with standard entity templates#32359DhairyasheelS wants to merge 7 commits intojhipster:mainfrom
DhairyasheelS wants to merge 7 commits intojhipster:mainfrom
Conversation
github-actions
bot
added
theme: maven
theme: dependencies
OmarHawk
reviewed
Feb 18, 2026
...lates/src/main/webapp/app/entities/_entityFolder_/delete/_entityFile_-delete-dialog.html.ejs
Show resolved
Hide resolved
OmarHawk
reviewed
Feb 18, 2026
DhairyasheelS
force-pushed
the
angular-user-management-standard-templates
branch
from
861e91a to
3221be9
Compare
Member
|
@DhairyasheelS following #32387 and #32379 many customizations should be dropped. |
DhairyasheelS
force-pushed
the
angular-user-management-standard-templates
branch
from
270e958 to
8f0700d
Compare
Author
|
Thanks @mshima for the feedback. I’ve reviewed #32387 and #32379 and understand that several customizations in this PR diverge from the standard entity template approach. I will:
I pushed incremental updates . Please let me know if there’s any specific pattern from those PRs you’d like me to follow more closely. |
DhairyasheelS
added a commit
to DhairyasheelS/DhairyasheelS-generator-jhipster
that referenced
this pull request
Feb 24, 2026
…tity templates - Add dedicated user-management template structure (entities/admin/user-management) with list, update, detail, delete, service, route and 20 template files - Use UserManagementService and User type in list component (no dynamic generics) - Customize user-management service: api/users, getUserIdentifier, UserManagementService - Set entityPage to 'entities/admin/user-management' for user management routes - Use userManagementEntityFiles section when writing user management UI - Relax code-workspace generator type (settings/launch to any) for ESLint Co-authored-by: Cursor <cursoragent@cursor.com>
- Use entity templates for admin/user-management instead of custom templates - Add builtInUserManagement branching in routes, list, detail, update, delete, service, routing resolve - Fix login regex in form service (escape backtick, raw EJS output) - Add jhipster-keycloak-test to .gitignore Closes jhipster#31891 Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…opy chain, list filter - List: trackIdentity returns item.login (string) when builtInUserManagement - List: infinite-scroll deduplication uses login when builtInUserManagement - List HTML: filter button queryParams use login; add hideListView to field filter - Service: PartialUpdate type uses login when builtInUserManagement - Service: single copy chain for create/update/partialUpdate when date + user mgmt - Service: update() response conversion for builtInUserManagement; fix search() pipe - List spec: trackIdentity test when builtInUserManagement; sort/defaultSort for id Co-authored-by: Cursor <cursoragent@cursor.com>
- List HTML: remove hideListView from field filter (property not in model) - List spec: use literal entity with login for trackIdentity test when builtInUserManagement Co-authored-by: Cursor <cursoragent@cursor.com>
…ority import, trackIdentity via service, spec update Co-authored-by: Cursor <cursoragent@cursor.com>
…tity templates - Add dedicated user-management template structure (entities/admin/user-management) with list, update, detail, delete, service, route and 20 template files - Use UserManagementService and User type in list component (no dynamic generics) - Customize user-management service: api/users, getUserIdentifier, UserManagementService - Set entityPage to 'entities/admin/user-management' for user management routes - Use userManagementEntityFiles section when writing user management UI - Relax code-workspace generator type (settings/launch to any) for ESLint Co-authored-by: Cursor <cursoragent@cursor.com>
…r CI - Use angularFiles.client for builtInUserManagement (same as other entities) - Routes: always use UserRouteAccessService and canActivate; no defaultSort for user-management list - List spec: use login for sort when builtInUserManagement (login,asc/desc) - List: single trackPrimaryKey (trackLogin) for all entities; remove trackIdentity branch - Unify trackPrimaryKey test in list spec for builtIn and regular entities Made-with: Cursor
DhairyasheelS
force-pushed
the
angular-user-management-standard-templates
branch
from
a28c165 to
d7b3661
Compare
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
3 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.
Use the same entity templates for User Management as for regular entities instead of custom admin/user-management templates. Add builtInUserManagement branching in routes, list, detail, update, delete, service, and routing resolve so login-based routing, setActive, and authorities keep working.
Closes #31891
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.