ordering of keys

[pkoppstein]

The README acknowledges the discrepancies between jq and gojq with respect to key ordering,
but there is no open "ticket" to track this issue, which I believe to be critical.
Having a ticket will also allow others to weigh in.

Based on my own personal experience and observations, I believe that one of jq's great strengths
(at least after jq 1.3) is that it supports the ordering of keys, while defining "object equality" without regard to key ordering.

The practical importance of supporting the ordering of keys is closely related to what I take to be
one of JSON's main goals -- to be readable and maintainable by humans.

[itchyny]

I understand the practical importance but unlikely to implement for now so closing. There are various difficulties here; no support in Go standard library, custom internal functions.

[ahochsteger]

@itchyny at least for a YAML roundtrip there would be support for ordered keys using MapSlice: https://pkg.go.dev/gopkg.in/yaml.v2#MapSlice
I've seen similar approaches to keep the order of keys using MapSlice for JSON too.
This is the last known issue to me to completely switch from jq to gojq.