Thanks for the information, Karl.
I have a couple more questions:
It looks like the format is being applied in cases where ordering might
not really matter, e.g. listing jobs as in the example I gave. (Or
perhaps order does matter here?)
Is there any more doc on the non-sugared format than
The output format did change, and the reason was because the "syntactic
sugar" format would not preserve ordering, so that if you output and
re-input, you'd lose information.
The more complex form is being used only where there is a possibility of
ordering confusion. It was always accepted as
Hi,
After installing MCF 2.12 I am seeing a change in the JSON response
format from the REST API.
Here's an example, from the URL mcf-api-service/json/jobs. I've isolated
a job which exists in both my 2.11 and 2.12 instances. 2.11 is on the left:
The 2.12 format feels "internal" and I
