@ul if you look more closely you’ll see there are 2 render passes in Om. One for the root and another for individual components. Note all of this stuff is subject to change and has already been changed for Om Next.

could you briefly explain, where is component rerender is triggered if only its state has been changed and not app state or anything else?

i use custom atom for state which does not notify watches if values has not been changed

and i think this plays bad with my component which rely on updating its state

component's state i mean

@ul component local state and app state are not connected in anyway by default

again this isn’t any different from React

it’s worth spending some time understanding exactly what React guarantees

Om just copies that and adds extra stuff

so, component rerender on local-state-only-change is handled by React itself?

no

just similar semantics

so i can't see the place in code which guarantees that rerender

if you want to understand what the semantics are read the React documentation

you can but I’m not going to explain the whole thing in this channel

just throw a link to line in the code into me

sorry I really don’t have time to do code walk through right now

okay, thanks anyway

if you just want to understand the guarantees I’ve already explained them

swapping atom renders from root

setting state only re-renders a single component

swapping references cursors only updates components watching the ref cursor path

that’s it

i created minimal case and issue because second guarantee is not satisfied in my case https://github.com/ul/om-local-state-re-render/blob/master/src/om_rerender_on_local_state_update/core.cljs

https://github.com/omcljs/om/issues/355

@ul right the watches have to get triggered, but this is not something we’re going to fix as I see no rationale for making this work at least in the old way of doing things.