This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-28
Channels
- # announcements (2)
- # babashka (21)
- # beginners (24)
- # calva (9)
- # cider (7)
- # clj-kondo (12)
- # clojure (116)
- # clojure-europe (5)
- # clojure-korea (2)
- # clojure-norway (3)
- # clojure-poland (1)
- # clojure-spec (5)
- # clojurescript (12)
- # cursive (12)
- # datomic (8)
- # google-cloud (4)
- # honeysql (16)
- # java (18)
- # lsp (10)
- # missionary (14)
- # polylith (12)
- # re-frame (13)
- # releases (4)
- # shadow-cljs (10)
- # sql (10)
- # testify (2)
I'm working on this new transformer thing that lets you build functions using data and I added a behavior that can spec check data while it's being constructed. What do y'all think about this transformer/spec api? It basically accumulates more and more spec constraints as transformers are derived from each other. Here you can see a transformer map that won't let a particular key be dissoc'ed from itself because of its spec: https://github.com/johnmn3/step-up/blob/main/src/step_up/alpha/transformer.cljs#L196 Any recommendations on how best to compose together specs from different map specs in an ad hoc manner? I'd like to keep it as an "open" system by default.
I guess I'll want to make the spec checking an option that can be turned off in prod or whathaveyou
Please ignore the ugliness of the error messages - those are temporary and were just for testing right now