This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-17
Channels
- # aws (10)
- # beginners (64)
- # boot (3)
- # cider (20)
- # cljs-dev (32)
- # cljsrn (6)
- # clojure (126)
- # clojure-dusseldorf (3)
- # clojure-finland (1)
- # clojure-greece (1)
- # clojure-italy (7)
- # clojure-poland (3)
- # clojure-spec (46)
- # clojure-uk (100)
- # clojurescript (37)
- # cursive (11)
- # datomic (6)
- # defnpodcast (2)
- # emacs (1)
- # events (3)
- # figwheel (2)
- # fulcro (20)
- # immutant (2)
- # jobs (1)
- # jobs-discuss (9)
- # keechma (3)
- # lein-figwheel (1)
- # luminus (2)
- # lumo (3)
- # mount (2)
- # off-topic (19)
- # om (3)
- # om-next (2)
- # onyx (20)
- # other-languages (55)
- # parinfer (11)
- # pedestal (8)
- # portkey (3)
- # protorepl (3)
- # re-frame (22)
- # ring (9)
- # rum (1)
- # shadow-cljs (82)
- # spacemacs (28)
- # sql (15)
- # test-check (15)
- # testing (2)
- # tools-deps (102)
- # vim (26)
I was trying to deal with this bug (https://github.com/clojure-emacs/cider/issues/1841), and in investigating it I discovered that test.check
refers to a namespace that it doesn't have in the definition of test-context-stacktrace
: https://github.com/clojure/test.check/blob/master/src/main/clojure/clojure/test/check/clojure_test/assertions.cljc#L12
I commented that line out, and my problem went away. It's not clear to me how to contribute or report that so, I'm mentioning it here
As I look at it more closely, I doubt it's that exact spot that helped; but, there are definitely several references to a clojure.test.check.clojure-test
namespace. I see only a clojure_test
directory, but no namespace
that’s due to someone monkey-patching clojure.test
leiningen does that
maybe others
While I did see this, I don't quiiiiite know what it means, nor what it implies about my project being a boot project
I've heard the term but only the context of 1) Ruby objects and 2) disapproval. Sometimes at once~
well this may be something similar but different, not sure. Leiningen reaches in and replaces the implementation of part of clojure.test, which breaks test.check’s expectation.
that’s a pretty dirty trick imo :)