This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Can one configure the json key order of the generated content json? #6759
Labels
type: feature
code contributing to the implementation of a feature and/or user facing functionality
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.
The text was updated successfully, but these errors were encountered: