Clojurians
#om-next
<
2018-01-22
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

kenny74409:01:06

hello guys, I have a conceptual question: 1. user modifies component A's state 2. user modifies component B's state, which in turn updates the properties of component A 3. now component A's state is old and doesnt match with its properties, causing the UI to show the old state, instead of the new props what's the om-next way to deal with this? should component A's state be modified along with component B's state in step (2)? PS: inherited quite a bit of om-next code and still learning the language + the framework

claudiu18:01:13

@kenny744 using mostly fulcro. But think it's the same in this case.

claudiu18:01:05

Transact accepts a list of keys and will refresh all components that use those keys.

claudiu18:01:23

Option B: send the transact as a callback from a parent component of A & B.