[Improvement]: Improve UX Based on Role Based Access Control
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Developer Portal
Please select the aspect the issue is related to
Aspect/UI (Frontend layouts, components, styling)
Suggested Improvement
Checked login with ap_viewer role and getting 403 for Create application, subscribe like buttons click as expected. However the buttons are enabled and clickable and getting the error after clicking only. Good if the buttons can be disabled if the operations are not allowed.
Related Issues
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Developer Portal UI by reproducing the behavior while logged in with the ap_viewer role, checking the Create application and subscribe controls. Trace where those controls determine availability and verify that operations not allowed for the role are visibly disabled rather than producing a 403 after clicking.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100