Do matching against decoded request values by default
Open
Nobody has claimed this yet.
breaking
enhancement
java
- Dominant language
- Java
- Stars
- 7.4k
- Forks
- 1.5k
- Avg merge
- 13h 10m
- Merged PRs (30d)
- 16
Description
Proposal
Currently matching happens before decoding, and it creates a lot of confusion for users. While it is a breaking change, it would make sense to change behavior in one of the upcoming releases.
References
Examples of issues: TODO
Contributor guide
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
The issue names no files, tests, or entry points. First clarify the affected request-decoding and matching path and collect the referenced examples; done should be defined as matching decoded request values by default with an explicit breaking-change scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100