This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-26
Channels
- # arachne (4)
- # beginners (70)
- # bigdata (1)
- # boot (373)
- # braid-chat (3)
- # cider (4)
- # cljs-dev (10)
- # cljsjs (6)
- # cljsrn (27)
- # clojars (11)
- # clojure (114)
- # clojure-austria (1)
- # clojure-czech (2)
- # clojure-dusseldorf (2)
- # clojure-greece (7)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-russia (15)
- # clojure-serbia (11)
- # clojure-spec (92)
- # clojure-uk (5)
- # clojurescript (183)
- # component (9)
- # cursive (28)
- # datomic (36)
- # editors (4)
- # emacs (1)
- # garden (11)
- # hoplon (155)
- # lein-figwheel (7)
- # mount (47)
- # om (97)
- # onyx (25)
- # proton (3)
- # rdf (3)
- # re-frame (80)
- # reagent (9)
- # ring-swagger (9)
- # spacemacs (1)
- # untangled (145)
- # vim (2)
is it possible to inline an import, rather than outputting a literal @import
?
or just include some raw CSS (then i can just slurp
)
Yeah, my inclination would be to go with slurp
and concatenate that to the generated output of garden.
😕 using lein garden
with :output-to
, really would not want to concat
i’m going to look into extending the garden compiler protocols and see if i can inject raw css that way
ah, I don’t have any experience using anything other than garden.core/css
or garden.core/style
for output.
Typically my process is rendering the garden stylesheet to an external file with (css {:output-to “…”} stylesheet)
when the web server first starts rather than relying on any leiningen plugin.
In which case concatenating to that external file becomes very easy because you’re not in a plugin environment and you can craft the function you need to spit
out whatever you like.
well. i’m really not looking to significantly change my build process to eliminate 1 HTTP request. 🙂
thanks tho