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

POST's should not require default params #875

Closed
bdunklau opened this issue Apr 12, 2012 · 1 comment
Closed

POST's should not require default params #875

bdunklau opened this issue Apr 12, 2012 · 1 comment

Comments

@bdunklau
Copy link

I was asked to create this issue after submitting this question http://groups.google.com/group/angular/browse_thread/thread/bb21293203c7c68f#

Apparently, when creating an angular.service, you have to specify default params in the second argument of $resource in order for the @-style POST parameters to be evaluated. If you don't specify default params, then your @params will be passed to the web server as literals as my post above shows.

@vojtajina
Copy link
Contributor

When a default value of a param is prefixed with @ it reads the value from the Resource instance object.
It works fine with default params for all actions:

$resource('some/:param', {param: '@readFromObj'});

However it does not work with defaults specified per action:

$resource('some/:param', {}, {post: {params: {param: '@readFromObj'}}});

petrovalex added a commit to petrovalex/angular.js that referenced this issue May 11, 2012
@mhevery mhevery closed this as completed in b712cd3 Sep 4, 2012
mhevery pushed a commit that referenced this issue Sep 5, 2012
- $resource should handle multiple params with same name
- ignore slashes of undefined parameters
- fix default parameters issue, mentioned in #875

Closes #875, 782
mhevery pushed a commit that referenced this issue Sep 6, 2012
- $resource should handle multiple params with same name
- ignore slashes of undefined parameters
- fix default parameters issue, mentioned in #875

Closes #875
Closes #782
mhevery pushed a commit that referenced this issue Sep 6, 2012
- $resource should handle multiple params with same name
- ignore slashes of undefined parameters
- fix default parameters issue, mentioned in #875

Closes #875
Closes #782
mhevery pushed a commit to mhevery/angular.js that referenced this issue Sep 7, 2012
- $resource should handle multiple params with same name
- ignore slashes of undefined parameters
- fix default parameters issue, mentioned in angular#875

Closes angular#875
Closes angular#782
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants