fix: Attempt to measure component after it has been unmounted #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…unmount - Added sensible defaults to ensure we return numeric values if for some reason we cannot get the measurements of the component - Cancel the debounced onResize and parseTextForTruncation when the component unmounts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR fixes an issue where the
MiddleTruncatecomponent is unmounted, but still attempts to read the measurements of the component in order to parse the text for truncation. This scenario could occur when theonResizeevent listener was triggered, but the component was unmounted before the debouncedonResizehandler was called.onResizeandparseTextForTruncationwhen the component is unmounted.