This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-17
Channels
- # bangalore-clj (1)
- # beginners (70)
- # boot (1)
- # cider (39)
- # cljs-dev (69)
- # clojure (56)
- # clojure-dev (1)
- # clojure-norway (1)
- # clojure-russia (4)
- # clojure-spec (1)
- # clojure-uk (10)
- # clojurescript (34)
- # clr (3)
- # community-development (3)
- # component (1)
- # datascript (1)
- # datomic (7)
- # emacs (1)
- # figwheel (3)
- # fulcro (5)
- # graphql (2)
- # hoplon (75)
- # jobs (4)
- # jobs-discuss (1)
- # luminus (15)
- # planck (3)
- # portkey (55)
- # re-frame (2)
- # reagent (2)
- # reitit (3)
- # ring (13)
- # ring-swagger (1)
- # shadow-cljs (72)
- # spacemacs (4)
- # tools-deps (2)
- # unrepl (7)
- # vim (2)
I'm getting started with fulcro after having looked into om next a year or so back. Really enjoying the documentation and power fulcro looks to give!
Been able to hook it into an existing project using aleph and websockets. I've done a simple remote read and answer from the server. When I pass the load fn {:target [:root/things]} it works, awesome! There is one peculiarity though. When not doing the load with target it just renders the initial state as props. But when I load with target, there is one re-render where the initial state is passed as props, ok, but then a render where the props are empty-obj/null, and then another re-render with the result from the remote.