You can now get the latest changes of clj-yaml as a git dependency! https://github.com/clj-commons/clj-yaml#use-as-git-dependency

I published a temp fork of SnakeYAML to io.github.borkdude and wrote a test showing that the leading zero is fixed: https://github.com/clj-commons/clj-yaml/pull/54 I'll update this PR once SnakeYAML 1.33 upstream comes out

I also deployed a temporary clj-yaml version from this PR branch: io.github.borkdude/clj-yaml {:mvn/version "0.7-1.33-next"} I'm going to test this one in bb now

$ clj -M:babashka/dev -e "(require '[clj-yaml.core :as yaml]) (yaml/generate-string [\"083\"])"
"['083']\n"

I published a new bb with the all new snakeyaml + clj-yaml fixes as a temporary dep until all upstreams are streamed down!

Great stuff @borkdude! 🚀

Cheers!

Also thanks for moving issues->discussions

Because I didn't know how mvn deployment to clojars worked, I compiled and deployed the lib using tools build 😆 https://github.com/borkdude/SnakeYAML/blob/053b63daa895294dcf55a745aa48f06dfff1dea4/build.clj#L48

ha! cool.

It's so nice that clojure.tools.deps can play nice just sitting alongside mvn.

@borkdude what motivated the change from flatland/ordered to frankiesardo/linked? https://github.com/clj-commons/clj-yaml/commit/f45afb231b89bfd2d5a8f60247c97e0da82e8171 ?

argh, wtf...?

Actually, I think this is a hanging commit out there.

that isn't part of the master branch. https://github.com/clj-commons/clj-yaml/blob/883d7262fe7bb7ce3f844aa7fd5da184104ea74e/deps.edn#L3

LOL So, let me amend, what motivated the experiment to move flatland/ordered to frankiesardo/linked?

no clue

😄

@grzm I found this: https://clojurians.slack.com/archives/C03S1KBA2/p1585601368388200?thread_ts=1585581040.368800&cid=C03S1KBA2 It had to do with the added binary size of clj-yaml in bb so I investigated the effect of that dependency

https://clojurians.slack.com/archives/C03S1KBA2/p1585582969369900?thread_ts=1585581040.368800&cid=C03S1KBA2 Arguably still an open question 🙂

lol

I think as long as it lets us write edn and make other systems happy with the yaml output, it's worth it

I have to (hatefully, reluctantly) agree.

it's just part of the blue collar bash-stained workplace toolset

English vs metric wrenches.

Past summer I went to the cloud. When I saw kubernetes, I almost jumped off a cliff. (kidding, I haven't touched kubernetes at all, but I like the joke)

Okay. Time for breakfast with people smarter than me. Thanks again!

I'm contemplating a new library which smoothens the gap between YAML and several other formats: SnakeOil :drum_with_drumsticks:

YAML causing you grief? JSON making you pull your hair out? Try SnakeOil! Act now and we’ll throw in XML support. Only 4 easy payments.