This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-10
Channels
- # beginners (15)
- # boot (15)
- # cider (6)
- # cljs-dev (231)
- # cljsjs (1)
- # cljsrn (26)
- # clojure (147)
- # clojure-argentina (1)
- # clojure-dev (8)
- # clojure-germany (1)
- # clojure-italy (26)
- # clojure-russia (2)
- # clojure-spec (83)
- # clojure-uk (154)
- # clojurescript (123)
- # conf-proposals (3)
- # core-async (5)
- # cursive (26)
- # datascript (21)
- # datomic (120)
- # emacs (2)
- # graphql (9)
- # hoplon (195)
- # instaparse (16)
- # jobs-discuss (1)
- # leiningen (8)
- # luminus (8)
- # lumo (7)
- # off-topic (17)
- # om (7)
- # om-next (3)
- # parinfer (121)
- # pedestal (5)
- # planck (13)
- # re-frame (11)
- # reagent (21)
- # ring-swagger (2)
- # spacemacs (28)
- # uncomplicate (3)
- # unrepl (7)
- # untangled (34)
- # vim (5)
re ^ I wonder if we could catch this kind of issues when loading build.boot
and print a message with a rough guide for debugging this stuff? e.g. mostly -b
and what to look for in the stack?
@richiardiandrea just as a heads up, I’m just running our project with https://github.com/bhauman/lein-figwheel/pull/537 and boot-figreload and it looks pretty good
@kommen thanks for checking! it would be awesome to write there this feedback as well
I would like to release boot-figreload
but can't without that fix...
Is it true that boot-cljs is slower if you split a large file into many smaller files?
Can we combine tasks by invoking one task in another? E.g.
(deftask foo ...)
(deftask bar
"foo and more"
[]
(foo)
...)
(deftask bar [] (fn [next-task] (fn [fileset] (next-task ((foo) fileset)))))
- call foo on fileset then call next task
(deftask bar [] (with-pre-wrap [fileset] ((foo) fileset)))
- another way
(deftask bar [] (fn [next-task] (fn [fileset] (let [foos-fileset ((foo) fileset) new-fileset (do-stuff foos-fileset)] (next-task new-fileset)))))
hm, those are all broken actually
i make gist
Oh…I guess I’ll need to read more about Boot. Thanks @alandipert!