Re:I don’t have time for coding challenges
by cameronh90 on Friday September 11, 2020 @10:50PM
(#24449401)
For E2E encrypted APIs, one could well argue that worrying about HTTP verbs is just wasting time for no good reason. POST (consistently) lets you attach a body too.
Just using POST for everything is a pattern I've seen becoming more popular recently.
Re:I don’t have time for coding challenges
by chrisandchris on Saturday September 12, 2020 @05:35AM
(#24451157)
No we can get into an endless argument whether verbs are abused or not...
IMHO, GET (as of today) gas the issue that it does not support a body. If I‘m executing a search (an idempodent action), how can I nicely pass a JSON object configuring the search? I‘ll just use POST for that... So then we‘re at the point where the url does not work anymore because we have a POST /findEmployee; POST /findContract; ... instead of GET /employee and GET /contract.
Maybe I‘m wrong here, but it doesn‘t like nice in my eyes using POST in that way.
Re:I don’t have time for coding challenges
by ulucs on Saturday September 12, 2020 @07:19AM
(#24451619)
The JS API's I used to develop in used a mix of query strings (for exact matches) mixed with JSON (for more complicated queries) all in the url parameters
Re:I don’t have time for coding challenges
by andreareina on Saturday September 12, 2020 @04:23AM
(#24450848)
Google Places API puts the key in a query parameter. Still don't know how I feel about that.
But, IMO, even if you don't know, it's the kind of thing you learn once in code review and then don't worry about again.