Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Shouldn't parse the question mark

See original GitHub issue

Also as documented, the question mark at the start of string shouldn’t be considered as a part of first parameter’s name.

This snippet:

queryString.parse('?code=123')

results {'?code':'123'}

Here is also a screen shot from the console:

Issue Analytics

State:
Created 2 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

4reactions

afshin-hoseinicommented, Apr 15, 2021

@sindresorhus

🤦🏻‍♂️ I am resigning today 🥲

2reactions

debaraj-baruacommented, Aug 30, 2021

I am SMRT

So I am not the only smrt one

I basically copied the package from the very place I was instructed not to.

Screenshot 2021-08-30 at 13 27 22

Top Results From Across the Web

Saxparser not parsing HTML numeric character reference ...

i use defaulthandler saxparser. system out in character method shows me a question mark for the numeric character references. i did lot of ......

Entering " (QUOTATION MARK) shouldn't cause parse error #4

One meant for developers, which leaves escape characters untouched. The developer should not be harassed with semi-intelligent parsing of "some" ...

Why *not* parse `ls` (and what to do instead)?

-q - Force each instance of non-printable filename characters and <tab> s to be written as the question-mark ( '?' ) character. Implementations ......

ParsingLs - Greg's Wiki

Why you shouldn't parse the output of ls(1) ... it turned the newline character in between the words "a" and "newline" into a...

"say 'what are you doing?'" is SF:ques and drops "say" in parse

A couple of questions about the construct “say '[something]'”: With the 2020 grammar I got 24 readings for “say 'what are you doing?...