ljharb/qs

Feature request: option for deciding how to parse query without argument

Open

#223 opened on Aug 18, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (8,015 stars) (744 forks)batch import
feature requesthelp wantedparsestringify

Description

Hi,

I was wondering if it would be possible to support passing an option for deciding how to parse queries without arguments? Currently url?foo can be parsed as either the empty string or as null. I am wondering if it's possible to have the parser treat a query without arguments as true.

Some background: I ran into a case in our codebase which does this, it seemed odd to me but apparently there's nothing in the standards that forbid queries without arguments. Are there more specific standards (e.g. the node implementation) that this library is trying to adhere to?

Thanks!

Contributor guide

Tech stack
javascript
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptUnderstanding of query string parsingqs library
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the discussion in this issue (#223) for any maintainer feedback on the desired behavior. The main parsing logic is in lib/parse.js. The implementation should add a new option to control how query parameters without values are parsed (e.g., empty string, null, or true). Ensure backwards compatibility by keeping the default behavior unchanged.