This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-30
Channels
- # arachne (1)
- # beginners (1)
- # boot (13)
- # cljs-dev (35)
- # cljsjs (12)
- # cljsrn (11)
- # clojure (77)
- # clojure-austin (14)
- # clojure-brasil (3)
- # clojure-france (1)
- # clojure-poland (4)
- # clojure-russia (23)
- # clojure-spec (39)
- # clojure-uk (14)
- # clojurescript (17)
- # cursive (16)
- # datascript (10)
- # devcards (1)
- # dirac (3)
- # editors (1)
- # emacs (4)
- # jobs (1)
- # jobs-rus (2)
- # luminus (5)
- # off-topic (1)
- # om (85)
- # parinfer (1)
- # perun (12)
- # re-frame (20)
- # reagent (4)
- # spacemacs (1)
- # specter (9)
- # yada (6)
looking at this one: http://dev.clojure.org/jira/browse/CLJS-1490
I can mark the macro-dependant files for recompilation, but it seems that the macros don’t get expanded again
so even though the files that depend on macros get recompiled, the macros have the old behavior?
seems kinda strange, but it’s what I’m seeing
@anmonteiro: well you have to re-evaluate the macro file
@dnolen: oh.. actually re-evaluate the macro file in the compiler?
@anmonteiro: yeah you need to reload that Clojure code
I was looking at Figwheel for inspiration, and it does load-file
indeed
OK, let me try that then
Cool, it works now
@bhauman: I suppose I am. As compared to what?
@bhauman: ah right. I suppose that in that case I would have to :reload-all
I wonder what behavior would be most appropriate /cc @dnolen
From my experience you either have to do the very simple case where a file with macros in it has direct cljs dependents or do the full namespace walk
@bhauman: I get it now. A dependant of a macro file changed, but that one has no direct CLJS dependants
So yeah, I’m only doing the simple case
I would say handle only the case where a file has macros in it, and it has direct cljs dependents
it’s what I’m doing. if external tooling wants to do the full namespace walk nothing prevents that
@bhauman: thanks for your input 👍
I’ve attached my patch to the issue http://dev.clojure.org/jira/browse/CLJS-1490
@dnolen: should we warn or hard error on this one? http://dev.clojure.org/jira/browse/CLJS-1474
@anmonteiro: hard error is fine since that can only lead to head scratchers
gotcha