This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-18
Channels
- # admin-announcements (3)
- # alda (1)
- # boot (85)
- # capetown (4)
- # cider (10)
- # clara (16)
- # cljsrn (3)
- # clojars (35)
- # clojure (83)
- # clojure-austin (8)
- # clojure-brasil (4)
- # clojure-canada (16)
- # clojure-greece (2)
- # clojure-ireland (7)
- # clojure-russia (23)
- # clojure-spec (22)
- # clojure-uk (151)
- # clojurescript (97)
- # core-async (10)
- # cursive (1)
- # datascript (7)
- # datomic (21)
- # defnpodcast (13)
- # devcards (3)
- # emacs (4)
- # events (3)
- # hoplon (18)
- # juxt (4)
- # leiningen (7)
- # mount (4)
- # off-topic (2)
- # om (1)
- # onyx (30)
- # planck (6)
- # proton (81)
- # re-frame (3)
- # reagent (9)
- # rum (10)
- # spacemacs (1)
- # specter (6)
- # testing (7)
- # untangled (66)
- # vim (84)
- # yada (23)
Is there anyone else pushing for re-frame to be cljc - ready? We are retrofitting it here. Why?, you ask? Because then you can do testing of your handlers and subscriptions from clojure, using clojure.test - in the same CI environment you're already using. No need for phantom js etc.
Many of the re-frame ns's can be cljc'd super easily. We simply fake the reaction and use atom (not ratom) instead
I made that comment while looking at some Reagent code I wrote that generates hiccup using a (for)
without a (doall)
and is working nicely. So I changed it to a (map)
which then also worked nicely. But I’ve got other projects where both ARE wrapped in a (doall)
so now I'm just confused. I’m going to take a step back and see if I can puzzle out what I’m seeing and why.