[Feature] Consider changing these requests from GET to POST

[alexghergh]

Since what these requests actually do better suits a POST method rather than a GET method, consider changing them.

The requests are:
GET {{host}}/api/groups/{{groupName}}/invite/{{inviteID}}, and
GET {{host}}/api/groups/{{groupName}}/invites/new.

[alexghergh]

The issue here is that the client currently uses GET requests, and the POST requests don't actually have a body, so until we figure this out, we won't work on this.

[StormFireFox1]

Firstly, I'd like to address that I'm starting my first bug sprint (you've been posting way too many bug reports recently that I can't just leave there), so I will probably not work on this until I deal with all the other bug reports. Secondly, let's see what I have to say about the two methods.

On 19/06/10 11:35AM, Alexandru Gherghescu wrote: The requests are: **GET {{host}}/api/groups/{{groupName}}/invite/{{inviteID}}** -%<-

Well, this does technically warrant a POST request, as generally accepting an invitiation *should* post a new resource on the server, so I will admit that this could be a POST request. I'll deal with it as soon as I'm done with the bug sprint.

**GET {{host}}/api/groups/{{groupName}}/invites/new**.

This one always returns a new invite, a new resource, and that's honestly a GET in my book. When you call for this endpoint, you do GET a resource, and, while technically the resource here is dynamic, it still stands that the verb used is correct.

…

-- Matei-Alexandru Gardus (Storm_FireFox1) https://stormhub.io