Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
https://stackoverflow.com/a/983458/...
I dunno... to me a get request shouldn’t contain a body.
I interpret get requests as needing to be as light as possible, and you should be able to express the resource you’re trying to access in the URL entirely. -
@Brolls
What if you want to get a list of resources and there are 10+ different filters for that? Would you pass all the filters as part of the url? -
@bitsnpieces depends on the type of filter. It could potentially be a number of child routes.
I agree that it’s hard to make REST fit certain things though.
I suppose this is why the JSON only API approach is gaining support in places.
Swagger does not send request body for GET calls.! WHAT THE FUCK..! And the argument supporting is get calls should not have any request payloads and rather should have response payloads since its a "get" call. Are you serious?? What if there are parameters to be passed which cannot be accomodated in the params or the header. Even though people are kind of literally abusing on their issues page still they adamantly refuse to add support for this.
Swagger you had high standards in my book. You just fell so deep down there is no coming back.
rant
fuck swagger