Check API consistency for GET/UPDATE/DELETE events

[fjenett]

Creating events is bound to group, all others are not:

POST /event_group//event

whereas:

GET /event/
UPDATE /event/
DELETE /event/

[mattes]

GET /api/v1/event/{id}.json
PUT /api/v1/event/{id}.json
DELETE /api/v1/event/{id}.json

... have no dependencies to an event group. The mentioned routes do not need to know their group id to get/put/delete the event. This is different from:

POST /api/v1/group/{event_group_id}/user/{user_id}.json
PUT /api/v1/group/{event_group_id}/user/{user_id}.json
DELETE /api/v1/group/{event_group_id}/user/{user_id}.json

... where the group id must be known in order to:

• adds a user to an event_group
• updates attributes for user <-> event_group relation
• deletes a user from an event_group

I think we should leave the routes as they are atm. But I am open for other opinions.

[mattes]

I close this ticket. Please re-open if necessary.

[fjenett]

I was proposing to let users do a POST /api/v1/event.json sending along a (required) event_group_id instead to make it consistent with the other calls. Could even just be a redirect internally if that is possible.

[mattes]

Please let me know, if you want to go this way and I will implement these routes. (with redirecting)

[fjenett]

I think it is syntactic candy. Let's add this only if we have time for it.