This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-05
Channels
- # admin-announcements (183)
- # aws (30)
- # beginners (22)
- # boot (301)
- # cider (19)
- # cljs-dev (3)
- # cljsrn (23)
- # clojars (15)
- # clojure (136)
- # clojure-italy (8)
- # clojure-nl (4)
- # clojure-russia (19)
- # clojured (10)
- # clojurescript (134)
- # component (48)
- # cursive (7)
- # datavis (4)
- # datomic (50)
- # devcards (6)
- # events (9)
- # jobs (1)
- # ldnclj (10)
- # lein-figwheel (19)
- # leiningen (1)
- # luminus (16)
- # off-topic (5)
- # om (151)
- # proton (60)
- # re-frame (10)
- # reagent (25)
- # remote-jobs (1)
- # slack-help (3)
- # spacemacs (1)
- # vim (1)
think i figured out a good way to build devcards for re-frame components that doesn’t rely on global state if anyone’s interested
short version: push the subscriptions out of the component itself and pass in a fn to do dispatch with
@peeja it seems like if you have a separate build for devcards and also put a cards.html into a resources directory that is only available at dev time you should be set
@spieden: it would be good to have a devcards reference page for reframe. I haven't used it yet so I my look at it soon lots of folks are wondering about this.
What about rendering re-frame components in devcards with global state, and "real" dispatch and everything? It would be kind of an "integration" devcard. I know this is complicated with re-frame because of the state, handlers and subscriptoins all being global... But perhaps it could work if each devcard is actually rendered in an iframe? I think @pandeiro suggested this idea to me some time ago, and I don't see why it could not work... What do you think about it?