Skip to content

Permission query performance issue #22678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shuangbaojun opened this issue Apr 17, 2025 · 3 comments · May be fixed by #22724
Open

Permission query performance issue #22678

shuangbaojun opened this issue Apr 17, 2025 · 3 comments · May be fixed by #22724

Comments

@shuangbaojun
Copy link

Currently, in the permission module, the query for permissions retrieves all permission groups and all definitions under each group at once. Is there a way to query only the definitions under the permission group that the user clicks on?

At present, fetching everything at once causes performance issues — and it becomes even slower when combined with multilingual support.

@shuangbaojun
Copy link
Author

@maliming

@maliming
Copy link
Member

  • Your ABP Framework version.
  • Your User Interface type (Angular/MVC/React... etc.) if the issue is related to a specific UI
  • Your database provider(EF Core/MongoDB)
  • Exception message and stack trace if available (check the logs).
  • Please share the steps and code to reproduce the problem.

@shuangbaojun
Copy link
Author

Framework:ABP 8.3.4
UI:Blazor

It is expected to provide an overloaded method for GetAsync that includes a permission group as a parameter, in order to address situations with many permission definitions. This allows the UI layer to perform asynchronous rendering based on the permission group. As shown below:

Imageqiwang

@maliming maliming self-assigned this Apr 19, 2025
@maliming maliming added this to the 10.0-preview milestone Apr 19, 2025
@maliming maliming linked a pull request Apr 21, 2025 that will close this issue
@maliming maliming modified the milestones: 10.0-preview, 9.3-preview Apr 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants