This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-18
Channels
- # beginners (22)
- # boot (12)
- # cider (3)
- # cljs-dev (12)
- # cljsrn (8)
- # clojure (101)
- # clojure-nl (5)
- # clojure-russia (13)
- # clojure-spec (5)
- # clojure-uk (15)
- # clojurescript (158)
- # cursive (5)
- # datascript (16)
- # datomic (8)
- # hoplon (11)
- # lumo (33)
- # off-topic (3)
- # om (25)
- # parinfer (1)
- # pedestal (8)
- # protorepl (4)
- # re-frame (8)
- # reagent (5)
- # specter (18)
- # sql (1)
- # testing (11)
- # timbre (1)
- # unrepl (2)
- # untangled (1)
So I made this abomination. Anyone finds this useful or really unnecessary? https://github.com/yonatane/spec-grind/blob/master/test/spec_grind/grind_test.clj
@yonatanel not a super bad idea, but add an additional function to all your conformers (`s/conform can take two args), so that we can unconform as well.
https://clojure.github.io/clojure/branch-master/clojure.spec-api.html#clojure.spec/unform
@tbaldridge I don't think there's a need for unform here. I use a few predefined conformers for coercion and they yield either a coerced value or ::s/invalid, and you can chain them with s/and without using unform.