This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-17
Channels
- # adventofcode (2)
- # beginners (153)
- # cider (14)
- # clara (9)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (124)
- # clojure-dev (9)
- # clojure-france (18)
- # clojure-greece (22)
- # clojure-italy (11)
- # clojure-nlp (5)
- # clojure-russia (9)
- # clojure-spec (21)
- # clojure-uk (40)
- # clojurescript (82)
- # core-async (12)
- # cursive (3)
- # data-science (2)
- # datomic (225)
- # devcards (8)
- # docs (2)
- # duct (1)
- # emacs (18)
- # figwheel (2)
- # fulcro (117)
- # graphql (13)
- # hoplon (10)
- # jobs (7)
- # jobs-discuss (7)
- # keechma (8)
- # leiningen (4)
- # off-topic (16)
- # om (2)
- # om-next (3)
- # perun (11)
- # precept (4)
- # re-frame (24)
- # reagent (2)
- # remote-jobs (8)
- # ring (2)
- # ring-swagger (9)
- # rum (42)
- # shadow-cljs (8)
- # spacemacs (3)
- # specter (7)
- # uncomplicate (10)
- # unrepl (58)
- # yada (9)
right now, it's tracking what file the result is compiled from, so yeah, other files being touched won't trigger a re-render
The other files are basically customizing the generated css...so abstracting would be to trigger a task based on when not just one but multiple files on the fileset change
perun will re-render a file if one of its :input-paths
changes, like here: https://github.com/hashobject/perun/blob/master/src/io/perun.clj#L298
lessc
uses that function to generate output paths, so for a quick fix, you could just wrap that function and add whatever you want to each entry's :input-paths
, in your own lessc
task, implemented almost exactly like perun's
for a longer fix, perhaps we could figure out a way for the end-user of of lessc
to modify :input-paths
, since for this kind of thing, it's not obvious to me how perun would know what files to watch
Yes I think the longer term idea is best. A regex to each task could specify what can retrigger a change or something...