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

Regrade problem #4

Open
pstaabp opened this issue Apr 5, 2013 · 2 comments
Open

Regrade problem #4

pstaabp opened this issue Apr 5, 2013 · 2 comments

Comments

@pstaabp
Copy link
Contributor

pstaabp commented Apr 5, 2013

Is the regrade problem just changing the grade (number)? If so can't we do this with a PUT?

@whytheplatypus
Copy link
Owner

I think maybe it could be included in the PATCH update for the user problem, rather than a separate call? I'm not really sure what patch does, maybe it should or could be post.

Quick db aside.. I'm guessing this is where we would want a nested problem inside the user object? Or maybe just a reference I'd and user specific metadata like grade?

@pstaabp
Copy link
Contributor Author

pstaabp commented Apr 6, 2013

So I thought the 4 http requests are POST, GET, PUT, DELETE that correspond to Create, Retrieve, Update and Delete, but then reading, it appears that PUT and PATCH do similar things and PATCH is a newer construct. I'm also thinking of it the backbone framework (http://backbonejs.org/#Sync).

Peter

On Apr 5, 2013, at 5:20 PM, whytheplatypus [email protected] wrote:

I think maybe it could be included in the PATCH update for the user problem, rather than a separate call? I'm not really sure what patch does, maybe it should or could be post.

Quick db aside.. I'm guessing this is where we would want a nested problem inside the user object? Or maybe just a reference I'd and user specific metadata like grade?


Reply to this email directly or view it on GitHub.

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