Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

$httpParamSerializerJQLike serializing differently than jQuery.param #11551

Closed
gabrielmaldi opened this issue Apr 12, 2015 · 0 comments
Closed

Comments

@gabrielmaldi
Copy link
Contributor

There's a difference when serializing nested objects:

jQuery.param({ myObject: { prop1: 5, prop2: { propA: 10 } } })

produces

myObject%5Bprop1%5D=5&myObject%5Bprop2%5D%5BpropA%5D=10

While $httpParamSerializerJQLike produces

myObject%5Bprop1%5D=5&myObject%5Bprop2%5D=%7B%22propA%22:10%7D

ASP.NET Web API understands jQuery.param but not $httpParamSerializerJQLike.

BTW, thanks for adding this feature, @pkozlowski-opensource! 😃

@pkozlowski-opensource pkozlowski-opensource self-assigned this Apr 13, 2015
@pkozlowski-opensource pkozlowski-opensource added this to the 1.4.0-rc.1 milestone Apr 13, 2015
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Apr 17, 2015
…n logic

Follow jQuery parameter serialization logic for nested objects.

Closes angular#11551
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Apr 18, 2015
…n logic

Follow jQuery parameter serialization logic for nested objects.

Closes angular#11551
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Apr 18, 2015
…n logic

Follow jQuery parameter serialization logic for nested objects.

Closes angular#11551
lgalfaso added a commit to lgalfaso/angular.js that referenced this issue Apr 19, 2015
…n logic

Follow jQuery parameter serialization logic for nested objects.

Closes angular#11551
@chirayuk chirayuk modified the milestones: 1.4.0-rc.1, 1.4.0-rc.2 Apr 24, 2015
netman92 pushed a commit to netman92/angular.js that referenced this issue Aug 8, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants