fix: prevent ScrollProvider from causing unnecessary rerender #899
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.
Changing from
useState
touseRef
to keep track of the list of callbacks registered to theScrollProvider
to prevent unnecessary top-down rerenders when a callback is added or removed. This swap fromuseState
touseRef
works because the event of adding and removing scroll event callbacks does not affect the presentation at all that would require a rerender. The code in the callbacks should be the only thing responsible for possibly changing state and requiring a rerender. This change does not impact the frequency or result of the callbacks when called.