This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-03
Channels
- # admin-announcements (7)
- # beginners (30)
- # boot (181)
- # cbus (1)
- # cider (55)
- # cljs-dev (8)
- # clojure (104)
- # clojure-dev (3)
- # clojure-japan (1)
- # clojure-russia (70)
- # clojurescript (139)
- # core-logic (4)
- # cursive (23)
- # datomic (25)
- # devcards (10)
- # events (11)
- # funcool (1)
- # hoplon (39)
- # jobs (10)
- # ldnclj (19)
- # lein-figwheel (21)
- # off-topic (4)
- # om (174)
- # onyx (46)
- # re-frame (25)
- # reagent (3)
- # yada (7)
does devcards mkdn-pprint-source
macro work with om next’s defui
macro?
coudl i just call the defui*
function?
https://github.com/Jannis/om-next-kanban-demo/blob/master/build.boot#L37 @jannis: Hey, I have a question about your boot/devcards setup: is the line above required? How does devcards use this? Seems strange to pass things in compiler-options that’s not actually a compiler option?
@martinklepsch: I followed the "Devcards without Figwheel" instructions on http://rigsomelight.com/devcards/#!/devdemos.core - but I might be confusing what it means by "compiler options"
Seems it’s required: https://github.com/bhauman/devcards/blob/master/src/devcards/util/utils.clj
Looks like a good fit for :closure-defines
@martinklepsch: yeah it does, this was written before closure-defines. I want this value available on the clojure side so I have access to it in a macro. Does closure-defines work this way??
Closure-defines are just regular vars/symbols so I think that should work.