Timeline for How to represent business logic in restful API
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2019 at 18:40 | comment | added | IMSoP | @RomanVottner I didn't downvote your answer, that was someone else; nor did I say it was wrong, just that it could be clearer about how to apply the principles to the concrete scenario in the question. Regarding this answer, what standard link relationship would you use in place of the custom one (which you're quite right, I just invented off the top of my head)? And could you clarify what you mean about PUT - are you suggesting that since it's not replacing all the fields, it should be a PATCH? | |
| Nov 23, 2019 at 18:32 | comment | added | Roman Vottner | So, you downvote my post by suggesting standardized ways of using link-relations (either registered link-relation names or Web linking extensions) and then use i.e. approve-promotion, a custom-one, yourself? This sounds a bit like a hypocrite to me in all honesty. How does your custom one, that is taken out of thin air, differ from one defined by Web linking extensions? Your PUT suggestion is also questionable in regards to RFC 7231 | |
| Nov 23, 2019 at 17:57 | history | answered | IMSoP | CC BY-SA 4.0 |