Hi, just noticed that squint doesn’t respect property order when emitting objects defined via the syntax {:key-1 "foo" :key-2 "bar"} . I believe some js code do relies on the order in which js objects literals are written, like https://github.com/ProseMirror/prosemirror-schema-basic/blob/master/src/schema-basic.ts#L8-L104. Couldn’t find a reliable source of truth whether/which ECMA specification do enforce a predictable property order https://stackoverflow.com/questions/30076219/does-es6-introduce-a-well-defined-order-of-enumeration-for-object-properties How do we feel about that? @borkdude did this come out yet somewhere (couldn’t find in squint issues)

@andrea712 hah, wow, really? well, the issue is that even when reading that map, the order is already lost since it's a clojure hash-map

yeah, I thought so

we could fix that maybe with #ordered/map {:foo "foo"} or so, in squint itself, can be done outside of the reader

but only if there is no other way and JS really relies on this

I’ll dig a bit deeper, I can work around the issue for the moment, thank you

I guess you could construct a JS object from a non-literal map as a workaround

user=> (js-obj "a" 1 "b" 2)
#js {:a 1, :b 2}

maybe js-obj isn't supported yet in squint? if not, we should add it