Skip to content

fix: refresh Angular permissions after resource updates#25110

Closed
enisn wants to merge 1 commit intorel-10.2from
fix/21899-resource-permission-refresh
Closed

fix: refresh Angular permissions after resource updates#25110
enisn wants to merge 1 commit intorel-10.2from
fix/21899-resource-permission-refresh

Conversation

@enisn
Copy link
Copy Markdown
Member

@enisn enisn commented Mar 18, 2026

Summary

  • refresh Angular app configuration after resource permission changes for the current user or one of the current user's roles
  • let abpPermission-based UI react immediately after save/delete instead of waiting for a full reload
  • support the permission visibility part of volosoft/volo#21899 and other resource-permission screens using the same component

Testing

  1. Open a page that uses resource permission management, such as AI Management workspaces.
  2. Change a resource permission for your current user or one of your current roles.
  3. Save or delete the permission and confirm the related Angular buttons update without a full page reload.

Copilot AI review requested due to automatic review settings March 18, 2026 08:43
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR ensures Angular UI permission checks (e.g., abpPermission) react immediately after resource-permission updates by conditionally refreshing the app configuration when the changed permission targets the current user or one of their roles.

Changes:

  • Inject ConfigStateService into the resource permission management component.
  • After save/delete, refresh Angular app state when the provider is the current user (U) or one of the current user’s roles (R).
  • Add helper methods to determine when an app-state refresh is necessary and to trigger it in the RxJS flow.

@enisn enisn requested a review from sumeyyeKurtulus March 18, 2026 08:47
@enisn
Copy link
Copy Markdown
Member Author

enisn commented Mar 18, 2026

Not needed in the current phase. Refreshing the page is OK for now

@enisn enisn closed this Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants