This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-29
Channels
- # architecture (14)
- # beginners (184)
- # boot (25)
- # cider (23)
- # clara (9)
- # cljsjs (13)
- # cljsrn (5)
- # clojure (140)
- # clojure-austria (1)
- # clojure-dev (24)
- # clojure-greece (15)
- # clojure-italy (7)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-sanfrancisco (10)
- # clojure-spec (39)
- # clojure-uk (28)
- # clojured (1)
- # clojurescript (26)
- # core-async (3)
- # cursive (13)
- # datomic (44)
- # docs (3)
- # emacs (31)
- # events (2)
- # figwheel (4)
- # fulcro (6)
- # graphql (2)
- # hoplon (5)
- # jobs (11)
- # juxt (4)
- # keechma (19)
- # leiningen (1)
- # off-topic (8)
- # om (8)
- # onyx (18)
- # parinfer (2)
- # re-frame (18)
- # reagent (24)
- # ring (4)
- # rum (2)
- # shadow-cljs (26)
- # sql (15)
- # timbre (6)
- # vim (2)
oh I think I misunderstood, I can't run the tests from the calling namespace but rather have to run them from the test namespace.
Does anyone know why IDeferred is considered unresolved? Could it be because IDeferred is defined in a custom macro definterface+
that calls definterface
only if not already defined? The code works otherwise.
@mattford Right, the command will run all tests in the current namespace. Once you’ve done that though, you can then run the previous test action from anywhere.
@yonatanel Yes, that sounds plausible. Does definterface+
look just like definterface
?
(defmacro definterface+ [name & body]
(when-not (resolve name)
`(definterface ~name ~@body)))
Actually, I did edit the manifold source to use the original definterface
and put it in checkouts
folder which Cursive is aware of, and still had the same problem. I'm not sure what I'm doing wrong.