Could be as simple as an editor macro, I guess

Hm ... maybe I should just do that in Clojure ...

isn't there a tool @U04V15CAJ wrote that can do this?

I guess you could use #CHB5Q2XUJ for this

Phew, been a while since I used zippers 😅 Seems to be able to do what I want, although I had to add some functions for creating comma-nodes. At least this experiment could lead to a simple PR, if nothing else

I had fun (and profit 🙂 ) with rewrite-clj on EOG, @U052XLL3A, just a testimonial 🙂

you don't have to use zippers necessarily, I use rewrite-clj to work with the raw nodes a lot of the time

Yeah, I'm trying both approaces, but I'm having a hard time understanding how to use the nodes api for some reason - it will allow me to comma-separate nodes, but then the convertion back to strings goes haywire

I think I could also add an option to #C04QVMQ39LG to let you create ordered maps instead of regular hash-maps from map literals

this would be a lot easier than rewrite-clj

Well, of course if I can get others to solve my problem, that's easier 😄 But won't you have the same issue, if you have regular, unordered hash maps as an intermediate structure, @U04V15CAJ?

no:

user=> (e/parse-string "{:a 1}")
:elements [:a 1]
{:a 1}

nice!

it first parses the elements and then creates the hash-map, I could just make that configurable

similar for set I guess

let me whip up a branch, then you can try if you want

sweet! I'd be happy to test it out!

$ clj -Sdeps '{:deps {borkdude/edamame {:git/url "" :git/sha "ce78f7b64381489c3feee7db40683cc5d0ec713d"} org.flatland/ordered {:mvn/version "1.15.11"}}}'
user=> (require '[edamame.core :as e])
nil
user=> (require '[flatland.ordered.map :as m])
nil
user=> (e/parse-string "{:a 1}" {:map m/ordered-map})
#ordered/map ([:a 1])

user=> (e/parse-string "{:x [{:a 1}]}" {:map m/ordered-map})
#ordered/map ([:x [#ordered/map ([:a 1])]])

with json:

user=> (j/write-str (e/parse-string "{:a 1 :b 2 :c 3 :d 4 :e 5 :f 6 :g 7 :h 8 :i 9 :j 10 :k 11 :l 12}" {:map m/ordered-map}))
"{\"a\":1,\"b\":2,\"c\":3,\"d\":4,\"e\":5,\"f\":6,\"g\":7,\"h\":8,\"i\":9,\"j\":10,\"k\":11,\"l\":12}"

Very nice! Works for me 🙂 TIL that clojure.data.json supports ordered maps

I think most tools just don't know the concrete type of the map, most core functions work against the interfaces behind it

Well cheshire as well - I guess it's just that the ordered map implements iteration in a certain way?

ISeq, IAssociative, etc

ok, I'll make a release, this is something I've wanted to support anyway and this felt like a good time :)

Great, thanks a lot for spending time on it 🙂

is there a need to make :set pluggable as well?

Generally I'd say yes. I've rarely used sets in config data, but they probably have their place

But for my use-case here, no

I'll just do it anyway

@U052XLL3A https://clojurians.slack.com/archives/C06MAR553/p1706613676471569

can I get some brownie points for this? 😉

sure ;)

dang... and usually Java is quite good when it comes to backwards compatibility.

(at least that is tell all the TS/JS people around me)

I was trying to keep up with the issue comments in clj-commons as it’s there as an issue. Not clear if it was ever merged or not.

Removed it for now, I can still call all my defmethods directly without any fuss, I just liked the queue there to handle the request load (not a problem I ever had 🙂 )

still does my head in that this was at roughly noon and that is looking due south (more or less). I wonder if I'll ever get used to being this far north.

that beach is lit up

It was more than I could look at

woweee. What beautiful colors, and foreground/background composition

Woah <3

Thanks very much 🙂