Escaped parameter not correctly parsed
Open
bug
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 156
- Avg merge
- 4d 43m
- Merged PRs (30d)
- 3
Description
Filing this issue for what @dilyanpalauzov found in #668 and #537
Contributor guide
Research direction
Start by reading the findings referenced in issues #668 and #537, then trace the escaped-parameter parsing path in the JavaScript parser. Reproduce the reported input and compare the parsed result with the expected parameter value; done means the escaped parameter is parsed correctly and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100