URLSearchParams iterator doesn't iterate in the correct order
Open
- Dominant language
- Go
- Stars
- 300
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
As a simplified implementation, Go's `net.url` package is used internally which represents query strings as a `map[string][]string` which is useful for representing the information, but doesn't guarantee ordering when iterating.
Contributor guide
Research direction
Start by locating the URLSearchParams implementation that uses Go's net.url package and represents query strings as a map[string][]string. Trace its iterator behavior and add coverage for the required ordering; done means iteration preserves the query parameter order consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100