updated so that objects are default unless [] are empty and updated test...#98
Open
updated so that objects are default unless [] are empty and updated test...#98
Conversation
…ests to verify it works
This was referenced Mar 20, 2014
Author
|
anything blocking this from being merged? I'd really like to remove the hacks that I have to add to my html |
Collaborator
|
Will check this in about 4 hours. I'm on the move right now. |
Author
|
Has this been merged in? It still passes build tests right? |
|
Just stumbled upon this problem too that number-like keys are lost when between brackets. So, any news on this? |
This file contains hidden or 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
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.
updated so that objects are default unless [] are empty and updated tests to verify it works
Basically the point of this is to make it work more like PHP and Rails.
Items[1]=on&items[4]=on
will now become:
{ items: { 1: on, 4: on } }
rather than
{ items: [on, on] }
Updated tests to make sure that it didn't mess up even when [] and [99999] was used.
items[]=on&items[]=on will still equal { items: [on, on] }