[Proposal] PATCH instead of PUT

[xtrasmal]

Please look at this stuff: https://speakerdeck.com/nicola/developing-restful-web-apis-with-python-flask-and-mongodb?slide=113

[taylorotwell]

Post a question or real issue, not a slideshow.

[frankmayer]

@xtrasmal you have the choice, choose whatever you like. Both PUT/PATCH are handled by the update action. Strictly speaking PUT should be mapped to replace and PATCH to Update but this direction was not chosen by Taylor. See this issue (blast from the past) in the old illuminate/routing repo: illuminate/routing#20

[franzliedke]

Taylor mentioned in that ticket that he took the same approach as Rails. This article says they do prefer PATCH for updates now.

Time to reconsider?

[xtrasmal]

@taylorotwell I posted a slideshow, because it is quite a complete presentation of a concept. If I had a question I would have put some more time into it. Before posting it here I considered posting this at the forums, but thought this would reach the right people. Maybe you understand. So excuse my slideshow, I just wanted to add something that might have slipped somebodies mind and could have been a useful contribution.
@franzliedke thank you for the links with useful background information. I'm pleased to see that our founding farter Taylor takes on very good decisions :) Great stuff. I will close this issue.

[franzliedke]

I was trying to say that your suggestion should be seriously considered...

[frankmayer]

@franzliedke 's pointing to the rails article may really be a call to reconsider, @taylorotwell. Since you made your decision back then based on the rails way of things, and since laravel is still in beta, it might be better to change this sooner than later.

[frankmayer]

@xtrasmal maybe keep this issue open, so we can discuss this and it doesn't fall off the radar?

[xtrasmal]

@frankmayer Opened it in case of further discusson.
@franzliedke I might have misread. I read that Patching or Putting is something that is purely up to how you handle a UPDATE.

Reopened for dicussion.

[taylorotwell]

I think we're pretty good here really. We basically take the same approach as Rails in this scenario with routing both PUT and PATCH to the update method of the resource controller.