metadata added by read-string (as compared to clj implementation). about babashka HOT 9 CLOSED

Well, project.clj isn't technically EDN.

from babashka.

@skat-kurt I recommend using something like edamame for this, which is built into babashka as well. You can tweak whatever you want to allow in your .ednish or .cljish file. E.g. if you want to have EDN + regexes but never a location, you can do this:

(require '[edamame.core :as e])
(e/parse-string "..." {:regex true :location? (constantly false)})

from babashka.

@skat-kurt It's not recommended to use read-string for reading EDN files. This is what we have clojure.edn/read-string for. read-string is for reading code.

from babashka.

Thanks, using clojure.edn/read-string works perfectly (and I should have known...)

from babashka.

Nonetheless, I'll try to align bb's behavior to clj's.

from babashka.

I'll have to stick with my original work-around for now. The original file I want to read contains a regex, which edn/readstring doesn't like

(edn/read-string "#\"test\"")

Results in the

java.lang.RuntimeException: No dispatch macro for: "

exception, mentioned in another issue as well. That behavior is identical with standard clojure though.

from babashka.

regexes aren't part of EDN, so if your file ends with .edn I would say this is just invalid syntax

from babashka.

You are right. A pity that the clojure.edn namespace isn't symetric. I mean, there is no clojure.edn/write-string function that could throw when serializing data to edn that cannot be expressed in it. I use pr-str instead, which happily writes regex etc.

Some background. The "edn" files form the basis to auto-generate leiningen compatible project.clj files and some of them need :userjar-merge-with in combination with regex, as seen in the example project.clj file https://gitlab.com/technomancy/leiningen/blob/master/sample.project.clj#L436. I'll find another way to express this in the source edn files, so that they become valid edn files and take it from there.

from babashka.

I think I'll go with introducing a reader tag for regex, so that the edn files at least become valid, while edn/read-string returns regex data. Something like the following.

(edn/read-string
            {:readers {'regex re-pattern}}
            "#regex \"the-pattern\"")

from babashka.