This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-12
Channels
- # arachne (1)
- # aws (2)
- # beginners (123)
- # boot (22)
- # boot-dev (8)
- # chestnut (3)
- # cider (38)
- # clara (36)
- # cljs-dev (148)
- # clojars (2)
- # clojure (76)
- # clojure-austin (2)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-russia (5)
- # clojure-spec (8)
- # clojure-uk (65)
- # clojurescript (45)
- # core-async (38)
- # cursive (9)
- # data-science (5)
- # datomic (28)
- # docs (1)
- # emacs (2)
- # fulcro (34)
- # hoplon (18)
- # jobs-discuss (7)
- # keechma (8)
- # lumo (5)
- # om (3)
- # onyx (31)
- # parinfer (1)
- # pedestal (1)
- # re-frame (20)
- # reagent (5)
- # ring-swagger (16)
- # shadow-cljs (56)
- # spacemacs (11)
- # specter (8)
- # sql (5)
- # unrepl (29)
- # yada (6)
I'm following the 2nd video, and for some reason I'm not getting the :ui/react-key key value when :inspect-data is set to true, just the :name and :ui/locale... any thoughts?
@macrobartfast 2.1+ doesn't use it anymore
I reworked the rendering to not need it. It was originally a workaround for the fact that there was no way to do a global re-render of an app in Om Next
I still need to update docs and I'm not sure what to do about the videos...probably just put a comment in the description.
oh, but perhaps I need to fix the defcard-fulcro macro...it may not have been updated to use the new stuff
great... thanks for that info... I don't think it's a show stopper for anyone watching the videos for now; they'll probably cruise past it.
it all looks ok to me in code. nothing should be broken. Let me know if something doesn’t actually work
@tony.kay I’ve found that there is no need for the post-mutation when the marker is set to false. Perhaps the behavior has changed since the first time this was written? http://book.fulcrologic.com/#_the_ui_and_post_mutation
That may be true..I’d have to re-visit the example code to know…glancing at it I don’t remember
Question about UI Refresh. I have a component that runs a transact! The defmuation only includes
(action [{:keys [state]}] .. )
and I'm seeing only the component refresh. However, if I add a remote to the mutation, I'm seeing the entire tree to that component rerender.Is there a way to avoid the entire tree from refreshing when I include the 'remote' call?
Hey @nickowsy. That sounds potentially like a bug in rendering optimization, but it isn't technically a bug in the model, since you should be thinking of the rendering as if it were a frame-based animation of the entire screen. Load markers also queue refreshes, and you might be using the old-style load markers and querying for those elsewhere?
hey @tony.kay! we have a defui w/ a recursive query. After the remote mutation, the top level component's props includes a change to 1 of it's children. That child was updated during the action
part of the mutation. However, the top level component re-renders causing re-rendering all it's children. On the re-rending of all the children, user input which hasn't be transacted yet gets blanked out.
Ah, I see...but it gets blanked out because you're using component-local state I'm guessing
if you were using component-local state and :ui/react-key then there could have been a bug...umount/mount of components loses local state, but that's fixed in 2.1+