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
{{ message }}
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.
I have a component that has a property of the currently selected file.
When the selected file changes it currently rebuilds the background data for Treebeard (held in a state) so that the component renders again (this is done to set the 'active' value on the correct node).
When we have large numbers of files in the tree (often we have ~=1000) there is a very noticeable delay (2-3 seconds) for the newly selected file to be shown
Is there a pattern for large datasets to set (for example) 'active' on a node without rebuilding all of the data?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a component that has a property of the currently selected file.
When the selected file changes it currently rebuilds the background data for Treebeard (held in a state) so that the component renders again (this is done to set the 'active' value on the correct node).
When we have large numbers of files in the tree (often we have ~=1000) there is a very noticeable delay (2-3 seconds) for the newly selected file to be shown
Is there a pattern for large datasets to set (for example) 'active' on a node without rebuilding all of the data?
The text was updated successfully, but these errors were encountered: