This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-14
Channels
- # aleph (16)
- # bangalore-clj (4)
- # beginners (19)
- # boot (27)
- # cider (81)
- # clara (2)
- # cljs-dev (343)
- # cljsrn (97)
- # clojure (224)
- # clojure-hk (1)
- # clojure-italy (25)
- # clojure-russia (5)
- # clojure-serbia (2)
- # clojure-spec (7)
- # clojure-uk (27)
- # clojurescript (97)
- # cursive (8)
- # datomic (48)
- # docker (1)
- # emacs (15)
- # hoplon (39)
- # jobs (4)
- # lumo (13)
- # off-topic (2)
- # om (66)
- # onyx (7)
- # parinfer (5)
- # pedestal (2)
- # play-clj (10)
- # protorepl (2)
- # quil (1)
- # re-frame (38)
- # reagent (33)
- # spacemacs (1)
- # specter (4)
- # sql (19)
- # test-check (31)
- # unrepl (4)
- # untangled (3)
@richiardiandrea should reloading for target nodejs work with boot-figreload?
doesn’t look like it https://github.com/boot-clj/boot-figreload/blob/master/src/powerlaces/boot_figreload.clj#L69
seems to work like charm with this https://github.com/boot-clj/boot-figreload/pull/9
The built-in notify task isn't making any sound for me. Is it correct to place it after watch
before reload
, cljs-repl
, cljs-devtools
and cljs
? Also I'm calling it like this (notify :audible true)
. Is this correct?
@kommen I did not test node and it was in the to-do list in the readme so thanks for trying and PR-ing
@richiardiandrea looks really good here
Awesome @kommen you could even tick the node box in the readme in the pr
just one note: I tried rebasing https://github.com/bhauman/lein-figwheel/pull/537 onto the current lein-figwheel master, but this causes crashes in in boot-figreload: Illegal argument exception handled for <boot cache path>/cljs_deps.js
kommen: ok so it is a no go then
kommen: I have to speak with Bruce on that one
ok, fwiw, I also get a warning with the current PR as it is now, and with the rebased PR this seems to escalate into a crash: Illegal argument exception handled for <boot cache dir>/cljs_deps.js
I’m happy to serve as your Guinea pig if you have something to test, we’ll be using that stuff internally already soon
Ok I will tell you whn I have something, but it can be next week or later because I am going to EuroClojure
ok cool nice! We will for sure I hope you can recognize me from the picture, I think I won't be able to recognize you from your avatar 😄
looks like its really hard to find a current picture of me online, I consider this as a success 🙂
here is one though https://twitter.com/musha68k/status/865290928583528449
Is there a boot idiom comparable to leiningen's :global-vars {*warn-on-reflection* true}
@grzm (set! *warn-on-reflection* true)
is a way, in build.boot or repl
if you’re using pod putting in boot-shim.clj is the way https://github.com/boot-clj/boot/wiki/Configuring-Boot#boot-shimclj-here-be-dragons
Cheers I tried that, and didn't see any warnings when running my tests. I don't think my code is that clean.
are you using boot-test? if so, it’s probably because boot-test runs your code in a pod… and you’d need to use boot-shim.clj to see an effect
interesting, looks like test
also takes a startup function argument. you could point that at a function that turns on reflection warnings
i think that’s preferable to boot-shim.clj
@mbertheau: from what you describe, it sounds like your usage of notify is correct. I don't know why it wouldn't be playing any sound. Maybe try using one of the other themes and see if that makes a difference?