This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-24
Channels
- # architecture (7)
- # beginners (73)
- # boot (4)
- # cider (48)
- # cljsjs (7)
- # cljsrn (27)
- # clojure (206)
- # clojure-boston (2)
- # clojure-italy (21)
- # clojure-nl (8)
- # clojure-spec (7)
- # clojure-uk (94)
- # clojurescript (126)
- # clojutre (7)
- # core-async (3)
- # cursive (7)
- # data-science (1)
- # datascript (4)
- # datomic (6)
- # duct (1)
- # emacs (19)
- # figwheel (1)
- # fulcro (31)
- # graphql (13)
- # jobs (5)
- # jobs-discuss (42)
- # keechma (4)
- # leiningen (10)
- # luminus (3)
- # mount (2)
- # nyc (3)
- # off-topic (37)
- # om-next (3)
- # onyx (45)
- # pedestal (2)
- # re-frame (4)
- # reagent (2)
- # reitit (16)
- # shadow-cljs (118)
- # spacemacs (10)
- # tools-deps (8)
- # vim (20)
hi everyone. whenever i use , t a
(run all tests) in spacemacs, most times it doesn’t ‘refresh’ the code. meaning it can’t resolve the newly added functions for example and then I have to quit and re-`jack-in` cider again. is there a work around to fix this?
@bravilogy - I think there's a "refresh" function bound somewhere under ,
, either in clojure-mode or cider-mode. You could try that before , t a
to see if it picks up your newly added functions etc. I'm just guessing here, though, because I haven't used , t a
before.
I sort of solved it by re-evaluating the buffer every time and + I’ve set it to automatically run tests whenever a namespace is loaded, which re-runs tests every time I re-evaluate the code
Cool, glad you figured it out!
That's really nice. I'll have to try that out the next time. I'm used to doing lein test-refresh
for autotesting. One of these days I need to just read the cider manual; I feel like I'm missing out on lots of good stuff.