Stanisław Barzowski

Order of list elements is always preserved. Do you mean the order of object fields?

There are some existing issues about that (#407, probably something on go-jsonnet side as well...). There are some good reasons not to do it (it shouldn't matter, JSON objects are...

@ilya-kolpakov Yes, that is correct. We certainly want to keep backwards compatibility w.r.t. how objects are manifested. So probably some additional hidden parameter on an object would be necessary to...

@arpitjasa-db Not really. You can take a look at the mailing list for the related discussion. If someone can come up with an acceptable proposal and wants to implement it,...

Nice! Some questions: * This is deep, right? I.e. preserve_order applies to nested object as well, right? * What exactly happens to the order of elements with `+`? Do you...

> I always put overriden fields after untouched, however i think + should keep old ordering of original field, i will change that Yeah. I expect the most common case...

Agreed. I like your approach and would be happy to make it official. > manifestDebug This _technically_ breaks some laws that `+` on object is supposed to follow (e.g. exposes...

How do you run it? This scripts depends on being run from inside `case_studies/kubernetes` directory.

I was thinking about some way to describe objects for the purpose of documentation and if we had that, I guess runtime checks using the same description would be quite...

I'm aware of some exploratory research, which hasn't been made public yet. I have also thought about it for quite a while and have a general idea how to fit...