@nblackburn Unless the API is actually deleting the resource and making it unavailable to access from any other calls, DELETE isn't really doing what it says it does.

It seems entirely possible that you might want to be able to cancel a booking, and still store a record of what was cancelled and the reason as to why.

While not the prettiest call, I would argue that there isn't a much better solution that could be implemented.

@gitpush I dont think i have seen a POST /resourceName/:id request implemented before, so I think it would initially catch some people off guard (which any well designed API should not do).

In regards to a PUT request, I see it as being appropriate, as long as there isn't any failable additional processing that occurs when you cancel.

@CurseMeSlowly
The only thing I see as being truly horrific about this API as it is implemented is the fact you provide a micrositeId (which presumably is already part of the booking resource), and the bookingReference (which is already supplied by the url) in the request body

Let me know what you think though. I love a good discussion on API design

@theuser @n3xus

What do you think of my keyring?

@tahnik while agree with this on personal projects. Every developer using their own indenting methods makes for an inconsistent codebase when collaborating. Code consistecy should always be strictly enforced, even of it means that some "spaces developers" have to use tabs

Also tabs > spaces

@ScribeOfGoD I am doing that too, its just sort of infuriating to see them pop up daily is all. The cathartic release of a rant has un-boiled my blood again

@kurtr My apologies, only did a cursory search. My passive aggressive offhand statement about verbatim reposting still stands however

If we are going to reupload comics verbatim from other sources, can we please at least make sure the original is linked.

This is from commitstrip not the facebook group. There are throusands of comics like this there, beautifully archived.