Improve UI policy grouping logic in control planes
Open
Nobody has claimed this yet.
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
UI grouping logic (Basic vs Advanced)
- Show in the policy landing view (not a new section) when:
x-wso2-policy-advanced-paramisfalse, or- annotation is missing.
- Show in Advanced/Additional Settings when:
x-wso2-policy-advanced-paramistrue.
- For nested properties:
- decision is based only on the root property annotation.
- do not evaluate child-level advanced annotations.
- if root is advanced, entire property block goes to Advanced.
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
No file or test is named. Start from the policy landing view and Advanced/Additional Settings grouping logic, then trace how root annotations are read for nested properties. Done means false or missing annotations stay in the landing view, true moves the whole root property block to Advanced, and child annotations do not affect placement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100