This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-29
Channels
- # announcements (17)
- # aws (12)
- # babashka (27)
- # beginners (85)
- # bristol-clojurians (1)
- # calva (16)
- # cider (3)
- # clara (7)
- # clojure (80)
- # clojure-europe (13)
- # clojure-italy (19)
- # clojure-nl (2)
- # clojure-norway (6)
- # clojure-poland (1)
- # clojure-spec (31)
- # clojure-uk (61)
- # clojurescript (29)
- # core-async (10)
- # cursive (7)
- # data-science (1)
- # datomic (29)
- # docker (3)
- # fulcro (120)
- # graphql (16)
- # hugsql (2)
- # leiningen (17)
- # luminus (2)
- # off-topic (36)
- # other-languages (3)
- # pathom (13)
- # re-frame (12)
- # ring (2)
- # rum (1)
- # shadow-cljs (126)
- # tools-deps (56)
- # vscode (5)
[com.wsscode/edn-json "1.0.4"]
is out! New things on this version:
- Add support for ::encode-value
for custom value encoding
- Add support for ::encode-map-key
for custom map keys encoding
Check it out at: https://github.com/wilkerlucio/edn-jsonΒ (edited)
The README says: "Transit produces JSON suitable for faithful round-trips in and out of EDN types, but itβs not good for consuming as JSON." Could you explain why Transit is not good for consuming as JSON?
yup π
the idea of this library is to be a middle term between preserving the original EDN and making it confortable for JSON tools to work with
one way to look at is, is imagine a version of clj->js
that can reverse EDN later with more fidelity, makes sense?
Yeah, thanks. A strange thing I just noticed:
(= (edn->json :keyword) "__edn-value|:keyword")
(= (edn->json {:foo 42}) #js {":foo" 42})
By itself, a keyword is encoded, but as a key map, it is not. It makes it indistinguishable from strings that start with a colon.yeah, that's a trade-off I was willing to make, given how common those are in the clojure world and how rare they are for regular JSON cases, more info: https://github.com/wilkerlucio/edn-json#encoding-decisions
Transit has :json-verbose
option that conserves the structure (don't uses lists for objects...) and is pretty comfortable to parse as json...
Oh, that's right! I completely missed that :json
and :json-verbose
differ in more than keyword caching.
seesm something very unusual when you using a data structure that you have in mind share with "javascript" (or to be interporable with json...)
Hi folks! Released [polvo/firestore-clj "0.1.3"]
It's a client for Google's Firestore database. It's quite idiomatic, supports both pulling data once and real-time data by materializing query results as atoms (and some lower-level stuff to). All functions are type-hinted so there's no reflection behind the scenes. Check it out at https://github.com/polvotech/firestore-clj
babashka, a native Clojure scripting tool, v0.0.67 adds clojure.test, hierarchies, multimethods and more: https://github.com/borkdude/babashka/releases/tag/v0.0.67 follow up in #babashka
Two bugfixes and one new feature: https://github.com/borkdude/babashka/releases/tag/v0.0.68