Fixed array.length > 2 bug and made camelCase optional #2
Conversation
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
camelCase should be optional and not forced for a general purpose application Array over 2 did not work
Owner
|
Two separate issues here:
Thanks for reporting this!
I will have a think about this. I do think I might end up removing the camel casing. |
hongymagic
pushed a commit
that referenced
this pull request
Jan 23, 2013
This is consistent with other $ methods such as: - $.serializeArray - $.serialize There is no reason why it should follow $.data conventions. Although that isn't hard to achieve.
Author
|
The removal of the camel casing is the optimal solution :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
camelCase should be optional and not forced for a general purpose application
Array over 2 did not work