This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-01
Channels
- # announcements (7)
- # babashka (10)
- # beginners (60)
- # clerk (4)
- # clojure (19)
- # clojure-conj (5)
- # clojure-europe (48)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (2)
- # clojurescript (12)
- # conjure (2)
- # core-async (24)
- # cursive (3)
- # datalevin (18)
- # events (1)
- # figwheel-main (5)
- # fulcro (22)
- # honeysql (29)
- # hyperfiddle (60)
- # jobs (3)
- # leiningen (18)
- # lsp (47)
- # meander (21)
- # missionary (6)
- # off-topic (35)
- # reagent (14)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (32)
- # sql (10)
- # transit (12)
what does "seems to interpret" mean
I assume you ran some code and got some result
the transit format spec says is the string tag and will be followed by a single char. # is special for a tag. ~ by itself is not a thing afaik
How would transit ever see “”? If the string “” is being sent, it gets escaped to ““. Otherwise the handlers and emitters should be spitting out valid tags.
It’s interesting. I don’t think transit (in the Java implementation) has checks for empty string tags (it does check for tags of length 1), and unable to find a registered handler, it just default to wrapping it up in the generic TaggedValue.
why does it hurt when I put my hand on the stove? :)