Page 1 of 1

Simple Queue output (old API) changed structure

Posted: May 8th, 2017, 11:57 am
by xenonism
I'm not sure this should be in Bug Reports, so I apologize if it shouldn't. Anyway...

The API was changed significantly with release 2.0.0, but according to the wiki, the old queue API (or "Simple Queue output") should still be available, to be deprecated in version 2.1.0 and eventually phased out one day. Despite this, while running version 2.0.0 and invoking the queue API with the "api?mode=qstatus", the JSON response doesn't include the "jobs" element and the "state" information is replaced by "status". Is this something that could be fixed, while third parties implement the new API system, or is intentional and I am missing something about the whole API switch?

Thanks in advance. :)

Re: Simple Queue output (old API) changed structure

Posted: May 14th, 2017, 5:54 pm
by safihre
Yeah sorry.. Thought it was the same but clearly wasn't. Not switching it back for 2.0.1 again, so hope external apps will make the switch..

Re: Simple Queue output (old API) changed structure

Posted: May 17th, 2017, 6:04 am
by xenonism
Thanks for your reply. If external apps just made the switch, they would break compatibility with <2.0.0, so having both structures available for a while would have been useful, but if it's not going to happen, at least now we know.

Re: Simple Queue output (old API) changed structure

Posted: May 18th, 2017, 6:17 am
by safihre
I meant the switch to the 'queue' API call, this one is the same throughout all versions :)

Re: Simple Queue output (old API) changed structure

Posted: May 18th, 2017, 9:22 am
by xenonism
Ah, ok! :) Understood.