On 01/22/2014 10:54 AM, Chris Johnston wrote:
> On Wed, Jan 22, 2014 at 11:36 AM, Andy Doan <email address hidden>wrote:
>
>> do we really want this API to be an HTTP GET and not a PATCH?
>>
> You aren't actually patching anything. I'm not sure though?
On 01/22/2014 10:54 AM, Chris Johnston wrote:
> On Wed, Jan 22, 2014 at 11:36 AM, Andy Doan <email address hidden>wrote:
>
>> do we really want this API to be an HTTP GET and not a PATCH?
>>
> You aren't actually patching anything. I'm not sure though?
Things are being changed:
219 + queryset. current_ workflow_ step = TicketWorkflowS tep.COMPLETED. value tepStatus. COMPLETED. value
220 + queryset.status = TicketWorkflowS
221 + queryset.save()
Normally a GET implies a read-only operation. This is doing writes. If
we move to a secure model someday - we could easily forget about this
method.