Skip to content

fix(parse): preserve empty parameter names - #41

Open
awais-ur-rehman wants to merge 1 commit into
unshiftio:masterfrom
awais-ur-rehman:feat/parse-empty-query-keys
Open

awais-ur-rehman wants to merge 1 commit into
unshiftio:masterfrom
awais-ur-rehman:feat/parse-empty-query-keys

Conversation

@awais-ur-rehman

Copy link
Copy Markdown

Summary

stringify({ '': 'value' }) produces =value, but parsing it currently returns { value: '' }. The parser requires a nonempty name, so it starts reading at the value instead. Allow an empty name when followed by = so this valid query parameter survives parsing and round-trips through the library.

The lookahead only admits an empty name before an equals sign, which is consumed by the match. Empty query separators remain ignored. Tests cover empty names before/between/after named parameters, ? and # prefixes, empty values, duplicate first-value behavior, malformed encoding and the round-trip above.

Testing

Validation: npm test (26 passing, 100% statement/branch/function/line coverage) and git diff --check, using Node.js 24.19.0. Four new regressions failed before the fix. The project has no separate build or lint command. Its Node.js 14/16/18 CI matrix was not run locally.

Assisted by OpenAI Codex for reproduction, implementation and test execution.

Breaking Changes

None.

Manual verification: parse(stringify({'': 'value with spaces', foo: 'bar'})) should preserve both keys and values; empty separators should still be ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant