You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah, nope not expected. If a key is only a number, it will be parsed as a member of a sparse array. If it only contains a number, it should be getting parsed as an object key, so that's where this bug exists.
Note that you can override the creation of an array at all by passing { arrayLimit: 0 } to the second parameter of Qs.parse
Is the above behavior expected? If yes, how to handle such keys?
The text was updated successfully, but these errors were encountered: