Hi.
Just a quick heads up. I'm going to be refactoring the api a bit shortly. I'll
be moving the api under an api/ path and trying to make use of a few more
features of the django rest framework.
There may of course be a need for a further refactoring events to allow for the
multi-product like feature to be built in.
This is roughly what I am looking at for the immediate changes (ignoring the
details of the available methods on each):
* api/
* api/users/
* api/users/<userid>/
* api/groups/
* api/groups/<groupid>/
* api/ticketfields/
* api/ticketfields/<fieldid>/
* api/tickets/
* api/tickets/<ticketid>/
* api/tickets/<ticketid>/ticketevents/
* api/tickets/<ticketid>/ticketevents/<eventid>/
The user and group models will at least initially come from
django.contrib.auth.models. We'll need to look at authentication again to
ensure that we are able to support this in a flexible manner.
I am also not completely sold on the need for the ticketevents to be on a
subpath of the tickets but it might be helpful if it is a closer match to the
mental model of how tickets are structured.
Cheers,
Gary
