This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-04
Channels
- # aleph (1)
- # aws-lambda (2)
- # beginners (30)
- # boot (2)
- # cider (7)
- # cljs-dev (65)
- # clojure (130)
- # clojure-denmark (1)
- # clojure-france (1)
- # clojure-germany (2)
- # clojure-greece (1)
- # clojure-italy (19)
- # clojure-kc (2)
- # clojure-nl (12)
- # clojure-poland (1)
- # clojure-russia (11)
- # clojure-spain (1)
- # clojure-spec (20)
- # clojure-uk (176)
- # clojurescript (65)
- # css (3)
- # cursive (8)
- # datomic (26)
- # editors (94)
- # emacs (10)
- # fulcro (66)
- # graphql (5)
- # midje (1)
- # off-topic (48)
- # om-next (2)
- # overtone (1)
- # re-frame (15)
- # reagent (6)
- # reitit (10)
- # shadow-cljs (68)
- # sql (3)
Thanks @claudiu - yes I did come across that page trying to understand what #om-next was doing - but the page doesn't reference the :value {:keys [:todo/list]} option from the om next docs, which made me wonder whether it was not used. Yes, I have looked at Fulcro a few times and might use it for the next project. I can see that Tony has rewritten the relevant parser/mutation from om-next https://github.com/fulcrologic/fulcro/commit/a8cd1ea3b1c2ed616814b011b5fe7a4bb0dcd30c
@felixb Yep. Fulcro has gotten about 6 months full-time from Tony last year. Crazy amount of improvements. Think the best place that highlights this is the https://www.patreon.com/fulcro/posts page