This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # alda (3)
- # beginners (109)
- # boot (24)
- # cljsrn (17)
- # clojure (41)
- # clojure-brasil (2)
- # clojure-china (1)
- # clojure-russia (19)
- # clojure-spec (9)
- # clojure-uk (5)
- # clojurescript (44)
- # cloverage (5)
- # core-async (3)
- # css (2)
- # datascript (6)
- # datomic (26)
- # emacs (2)
- # events (10)
- # hoplon (24)
- # lambdaisland (1)
- # om (2)
- # onyx (16)
- # other-languages (10)
- # proto-repl (2)
- # re-frame (14)
- # spacemacs (2)
- # untangled (4)
- # videos (1)
Hi all. Is there instructions on uninstalling boot? I think I hand installed it at some point, and now want to install the brew version.
@underplank: You should be fine with just deleting the binary, you can also clear the
i'm trying to write a boot task for cloverage and that was pretty simple as a core task, but i want to stick it into a pod because it uses a weird version of the reader most likely to cause problems for some projects
it uses (.getResourceAsStream (clojure.lang.RT/baseLoader) [...]) to get it's (re)sources and i wonder how i get the sources of the project itself into the env of the pod
is that idiomatic?
(pod/with-eval-in worker-pod (doseq [ns '~namespaces] (require ns))
seems like it. is there any practical difference to (.require pod ^String ns) beforehand?
what is the usual handling for test namespaces? do people put them into :source-paths or not?
@fossifoo: normally I just make a task for that
(deftask testing  (set-env! :source-paths #(conj % "test")) identity)
then the task that actually runs the tests is just
(comp (testing) (boot-test/test))
man, this lettle boot excursion sure escalated quicker into an involved project than i expected XD
It's more common to have a testing task as Antonio described than having a task that adds another directory via an option
i'm in the process of writing a "cloverage" task for measuring code coverage and that needs that information as well because you only want "main" code to be instrumented and reported
@fossifoo: I don’t really know how the internals of cloverage work, but can’t you assume you’ll have all the info you need in your task?