Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doing a put includes unintended data #41

Closed
JonAbrams opened this issue May 3, 2013 · 2 comments
Closed

Doing a put includes unintended data #41

JonAbrams opened this issue May 3, 2013 · 2 comments
Assignees

Comments

@JonAbrams
Copy link

When doing a PUT using an existing object, there are fields being sent in the request payload that were not part of the object that was originally fetched.

e.g. some keys that shouldn't be there when being sent: parentResource, restangularCollection, and route.

Do you think it makes sense to strip these keys from the object before making the PUT call?

@mgonto
Copy link
Owner

mgonto commented May 3, 2013

It actually makes total sense. I've been pushing them because my server ignores them, but it makes total sense not to send them

@ghost ghost assigned mgonto May 3, 2013
@mgonto mgonto closed this as completed in 45991c7 May 3, 2013
@JonAbrams
Copy link
Author

Nice, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants