You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When lajt discovers changes in the ::pull op, make it easy to get the focused query for the data that has changed, such that one can map the focused query to the deepest component in the UI tree.
If PeopleList has rendered some people and the :person/primary-email changes for any of those people, the ::pull op should recognize that [:person/primary-email] in query [{:people [:person/primary-email]}] belongs to a component of PersonItem, and it should be able to re-render the specific one that has changed (maybe by ident?).
The text was updated successfully, but these errors were encountered:
shouldComponentUpdate is not sufficient as parents will have their render triggered, even though only the component that cares about :person/primary-email in this case, should have to be re-rendered.
When lajt discovers changes in the
::pull
op, make it easy to get the focused query for the data that has changed, such that one can map the focused query to the deepest component in the UI tree.Example:
If PeopleList has rendered some people and the
:person/primary-email
changes for any of those people, the::pull
op should recognize that[:person/primary-email]
in query[{:people [:person/primary-email]}]
belongs to a component ofPersonItem
, and it should be able to re-render the specific one that has changed (maybe by ident?).The text was updated successfully, but these errors were encountered: