Passing ref node to the onChange callback fn in useIntersectionObserver #617
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.
Context
Since the breaking change in the
useIntersectionObserver
hook in v2.13.0, we no longer have to pass a ref to the hook. Instead, it exports the callback ref for us to bind to the DOM node. However, using the callback ref loses the ref node access at the same time. For instance, the user might want to have some side effects on the ref node itself when it is intersecting. It would be helpful if the ref node were passed to theonChange
callback so we have access to itChanges
useIntersectionObserver
Example