4 ms·
Thank you! it is actually enlightening :) I think it's a little bit awkward to not use put, patch, delete... I wonder however if my server must follow the same
by GoodbyeEarl 10y ago
Thank you! it is actually enlightening :)
I think it's a little bit awkward to not use put, patch, delete... I wonder however if my server must follow the same technique, if not how to wire a delete endpoint to handle a form post and so on. I'll try to handle a form using only get and post sometime just to see how it works. Thank you!
- flukus 10y agoWell you just made me feel old. For put/patch/delete you can just as easily wire different options to different URL's. We had URL's like /Foo/Delete?43. It may be awkward in a particular framework but it's about as simple as things get. I've always hated put/patch/delete because it tends to result in data centric UI's instead of workflow centric ones.
- GoodbyeEarl 10y agoHmm now that you mentioned I realized I've seen this pattern before but I've never given it a thought. I'll definitely try it sometime, it seems to work pretty well. BTW sorry for make you feel old, it was not my intention haha
- GoodbyeEarl 10y agoHere it is https://github.com/viniciusCamargo/express-crud-barebone https://github.com/viniciusCamargo/express-crud-barebone here is my try on this approach to server requests. Any suggestion would be welcome! :)