This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-13
Channels
- # bangalore-clj (1)
- # beginners (40)
- # boot (22)
- # clara (19)
- # cljs-dev (265)
- # clojure (160)
- # clojure-dev (6)
- # clojure-italy (5)
- # clojure-russia (47)
- # clojure-spec (10)
- # clojure-uk (63)
- # clojurescript (88)
- # core-async (8)
- # cursive (54)
- # datomic (48)
- # emacs (32)
- # garden (3)
- # graphql (29)
- # hoplon (54)
- # jobs (1)
- # klipse (4)
- # luminus (5)
- # lumo (21)
- # mount (5)
- # off-topic (16)
- # om (2)
- # pedestal (10)
- # play-clj (1)
- # portkey (32)
- # re-frame (21)
- # reagent (48)
- # rum (1)
- # spacemacs (4)
- # sql (3)
- # unrepl (5)
Several people on this channel have asked about pretty-printing spec failures. I’ve just released Expound, a library that formats clojure.spec errors https://github.com/bhb/expound
bbrinck: great great great thanks!
I’ve got a lot more features planned, but hopefully this first release is useful to people on this channel
cc @samueldev (who also asked about this awhile back)
How can I constrain a multispec to a specific key? With the event example in spec guide I’ve tried this: (gen/sample (s/gen :event/event {:event/type #(s/gen #{:event/search})}))
which doesn’t work
Solved it using gen/fmap
to constrain the type, wondering if more succinct solution is available though.
@bbrinck: awesome!! I’ve been wanting something like this for a long time… Another thing that might be useful is integrating this into prone for rendering spec errors in stack traces over http (in dev): https://github.com/magnars/prone