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
Just opening the discussion here: could it be possible to implement a way to re-render the tree but from one specific node?
I know that diffing the whole tree is not that costly but on large nested apps and combined to redux' O(n) nature when solving actions, toggling a simble combo box might have a disproportionate cost.
I tend to use cursors and a single atom as my store and know precisely which part of the state has been updated when an action is triggered. So I am wondering whether there could be a way to re-render the tree from a given node when it is known.
The text was updated successfully, but these errors were encountered:
There was some discussion about this in #346 and #337. It should be solvable, and should be a renderer-specific optimization. It'll still need to walk down the tree from the top, but we'll make sure they're skipping as many sub-trees, diffs, and patches as possible.
Just opening the discussion here: could it be possible to implement a way to re-render the tree but from one specific node?
I know that diffing the whole tree is not that costly but on large nested apps and combined to redux'
O(n)
nature when solving actions, toggling a simble combo box might have a disproportionate cost.I tend to use cursors and a single atom as my store and know precisely which part of the state has been updated when an action is triggered. So I am wondering whether there could be a way to re-render the tree from a given node when it is known.
The text was updated successfully, but these errors were encountered: