Update all policy definitions to support advanced params and improve config annotation name
Open
Nobody has claimed this yet.
Type/Improvement
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Current Limitation
Policy properties does not have a way to mark a property advanced
Suggested Improvement
At root property level under parameters.properties:
x-wso2-policy-advanced-param:true|false- If missing, treat as
false.
- If missing, treat as
For config-linked defaults:
- Rename annotation key from
wso2/defaultValuetox-wso2-policy-default-config. x-wso2-policy-default-configwill be the standard key going forward.
Version
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 by locating all policy definitions and the handling for parameters.properties, then find where the existing wso2/defaultValue annotation is read. Done means advanced parameters default to false when omitted and the standard default-config annotation is supported consistently across policy definitions.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100