Can one configure the json key order of the generated content json? #6759
Description
We use github as the backend and have scripts managing the content jsons generated from decap-cms. Currently, in our script, we generate the jsons with keys in the order of defined in the config.yml file.
The issue we have is when we review the changes either done via out script (or afterwards changes done via the decap-cms UI), it is difficult to know what values got changed as the PR shows a lot of moved fields.
If the current decap-cms's output json key order is not configurable, then do we know what order it follows?
Thank you.