[file-tree] Refactor useFileTreeInstance use of refs #285
+317
−193
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description / Motivation
Consolidates the
useFileTreeInstancemount/unmount and options change logic into a single ref callback, eliminating the need for theuseStableCallbackutility. Also removed the unused forceClientRender logic.Typically we try to avoid
useEffect, and anything tied to the lifecycle of a node is usually better done using a ref callback.Changes:
The ref callback now handles both lifecycle events by including options and prerenderedHTML in its dependency array. When these change, React calls the cleanup function then re-invokes the callback with the same DOM node, allowing detection and handling of options changes.
Example page changes:
startTransitionfor non-blocking updates.Tests
Type of changes
first discussed with the dev team and they should be aware that this PR is
being opened
You must have first discussed with the dev team and they should be aware
that this PR is being opened
Checklist
contributing guidelines
bun run lint)bun run format)bun run diffs:test)How was AI used in generating this PR