This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-12
Channels
- # announcements (5)
- # babashka (1)
- # beginners (193)
- # calva (79)
- # cider (18)
- # clara (4)
- # clojure (38)
- # clojure-europe (12)
- # clojure-france (8)
- # clojure-nl (12)
- # clojure-sweden (1)
- # clojure-uk (50)
- # clojurescript (37)
- # conjure (30)
- # cursive (3)
- # data-science (2)
- # datalog (7)
- # datomic (12)
- # events (2)
- # expound (3)
- # figwheel-main (1)
- # fulcro (45)
- # graalvm (1)
- # jobs (1)
- # jobs-discuss (11)
- # luminus (1)
- # malli (5)
- # off-topic (32)
- # reagent (6)
- # reitit (32)
- # shadow-cljs (25)
- # spacemacs (2)
- # sql (22)
- # vim (6)
@cfleming would you please take a look at this problem above? i can submit a github issue. we use clojure spec for business entity and logic validation at work. as we all know, libraries like expound make clojure spec and it’s error messages a lot nicer and friendlier to work with. we have a workaround (force-flushing output stream using a prn
) but since it’s not something you would do normally, it gets tedious and tiring overtime, not to mention forgetting to do it completely and getting confused all over again. this is also one of the bugs (including being bombarded with cursive exceptions at least 100 times a day) that cause eye-rolls from people who are just skeptical about everything clojure. thanks in advance!