fix: nested repeated array syntax (#43) #44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #42 Essentially we had two bugs 👀 Bug 1: if you have repeat syntax when using bracket-notation, but only had one key, we would _not_ create it as a string. For example: ```ts parse('foo[]=1', opts); // {foo: 1} - wrong! parse('foo[]=1&foo[]=2', opts); // {foo: [1, 2]} - right! ``` Bug 2: if you have repeat syntax following an index-nested member, we would not parse it correctly. For example: ```ts parse('foo[bar][]=1', opts); // {foo: {bar: 1}} - wrong! // expected: {foo: {bar: [1]}} ``` These should both now be fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #42
Essentially we had two bugs 👀
Bug 1: if you have repeat syntax when using bracket-notation, but only had one key, we would not create it as a string.
For example:
Bug 2: if you have repeat syntax following an index-nested member, we would not parse it correctly.
For example:
These should both now be fixed.