Skip to content

qs.parse generates invalid and unexpected boolean values in some special cases #425

@n8tz

Description

@n8tz

Hi !

We found an unexpected qs.parse output with a boolean as the value and a value as the key using a specific query string construct.

The bug seems to occur when qs.parse needs to transcribe a property that has already been created with an object as the value.

Here an simple example of this behavior :

qs.parse("foo[bar]=stuffs&foo=123")

will output :

{ foo:{ '123': true, bar: 'stuffs' } }

Hgd :)

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions