This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-07
Channels
- # announcements (2)
- # babashka (38)
- # beginners (38)
- # calva (4)
- # cider (1)
- # clj-kondo (43)
- # clojure (50)
- # clojure-dev (39)
- # clojure-europe (4)
- # clojure-spec (4)
- # clojure-uk (2)
- # conjure (6)
- # core-async (5)
- # core-typed (3)
- # data-science (2)
- # datomic (6)
- # depstar (4)
- # emacs (1)
- # events (2)
- # fulcro (4)
- # jobs-discuss (4)
- # luminus (1)
- # off-topic (5)
- # re-frame (14)
- # shadow-cljs (8)
- # sql (8)
- # tools-deps (22)
What was the take on spec and coercions again - spec isn't meant to do coercions of values (during conformation), rather it only validates or conforms values, right? Then what is the opinion on a library like this one? https://github.com/exoscale/coax
My reading of comments by Alex, at least, is that Specs should not do coercions, but libraries that infer coercions from Specs, and do those coercions "outside" Spec are a good way to do stuff.
Our "web specs" library does the coercions internally in the Specs ("bad") but I've been looking at moving to spec-coerce
instead (or maybe coax
) and deprecating our library @borkdude