This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-04
Channels
- # announcements (5)
- # beginners (56)
- # calva (2)
- # cider (30)
- # circleci (2)
- # cljsrn (90)
- # clojars (3)
- # clojure (18)
- # clojure-dev (9)
- # clojure-europe (3)
- # clojure-greece (14)
- # clojure-ireland (6)
- # clojure-italy (6)
- # clojure-nl (7)
- # clojure-norway (1)
- # clojure-spec (1)
- # clojure-sweden (3)
- # clojure-uk (14)
- # clojurescript (52)
- # cursive (5)
- # data-science (9)
- # datomic (3)
- # emacs (26)
- # expound (11)
- # figwheel (3)
- # figwheel-main (6)
- # fulcro (24)
- # garden (1)
- # graalvm (101)
- # liberator (1)
- # mount (1)
- # off-topic (1)
- # pathom (27)
- # portland-or (2)
- # reagent (13)
- # reitit (2)
- # ring (1)
- # shadow-cljs (10)
- # spacemacs (11)
- # sql (6)
Hi all, is there a good way to a) use custom opts (disabling printing specs) b) use expound to format some but not all spec errors (only the ones intended to be read by operators of the system) Browsing through the code it seems that you can only set custom-opts via set! or alter-var-root with custom-printer which would effect all spec errors
@dev964 Are you looking to use spec to print out instrumentation errors or errors on some data that you have in your program?
the second one
and I ended up not using expound in the end …
Would binding
work in your case?
(binding [s/*explain-out* (expound/custom-printer {:show-valid-values? true})]
(s/explain (s/coll-of string?) ["" "" 3]))
yes, would work - but it was easier to construct the messages myself this time