This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-16
Channels
- # architecture (12)
- # aws (8)
- # bangalore-clj (1)
- # beginners (172)
- # boot (25)
- # chestnut (3)
- # cider (15)
- # cljsrn (5)
- # clojure (170)
- # clojure-india (1)
- # clojure-italy (21)
- # clojure-nl (87)
- # clojure-romania (3)
- # clojure-sg (1)
- # clojure-spec (1)
- # clojure-uk (79)
- # clojurescript (79)
- # cursive (2)
- # datomic (29)
- # dirac (26)
- # emacs (7)
- # fulcro (13)
- # jobs (4)
- # juxt (22)
- # lein-figwheel (1)
- # leiningen (2)
- # lumo (39)
- # nrepl (1)
- # off-topic (54)
- # onyx (124)
- # pedestal (1)
- # planck (4)
- # portkey (1)
- # re-frame (36)
- # reagent (2)
- # ring-swagger (8)
- # shadow-cljs (107)
- # spacemacs (1)
- # specter (25)
- # sql (7)
- # tools-deps (5)
- # vim (10)
- # yada (25)
2.5.5-SNAPSHOT is on clojars. This is a test release of Wilker’s patch to mutation merges with tempids.
Anyone else having issues with the shouldComponentUpdate
-lifecyclemethod?. It seems like im getting react-props
instead of fulcro-props
when the lifecycle method is being called.
:shouldComponentUpdate (fn [next-props next-state] ..)
I looked into the default implementation of this lifecycle method in fulcro.client.primitives and was able to retrieve the props in the same way: (.-props (gobj/get next-props "fulcro$value"))
Also noticed that there is no reshape-fn for this lifecycle method, might this be the problem? https://github.com/fulcrologic/fulcro/blob/develop/src/main/fulcro/client/primitives.cljc#L252
The only thing I've ever wanted to override that for is to set it to false for turning off subcomponent rendering for things like d3. I did not notice the props we're right. The code for it should be identical to that from Om Next, since that's where it came from originally.
The built-in behavior is able to short-circuit if the props have not changed...so there should really rarely be a reason to override it. It should, of course, be fixed if it is broken, but in 3 years I've not seen anyone say anything, which sorta indicates no one is overriding it
yeah, the missing reshape is why you're seeing react low-level stuff...that should be fixed.
Great, thats why I was doubting if I was doing something wrong, how could no one have ran into this issue. I did find this though: https://github.com/omcljs/om/issues/816. Someone did ran into it in 2016
funny, and he closed it thinking it was “his problem” 🙂 So, Om Next still has the issue
hi everyone, I've been working on a full-stack implementation of the famous Realworld app with fulcro on the frontend and Duct+Walkable+Postgresql on the backend
It's nearly complete. Progress is reported here https://github.com/walkable-server/realworld-fulcro/issues/1
Would be great if anyone can pitch in 🙂
The experience with Fulcro so far is superior. Many thanks to Tony Kay and Wilker Lucio for your hard work