Generate copyable text lazily to improve performance #22
Conversation
This file contains hidden or 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
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.
Right now,
copyTextis generated for every row in the table on every re-render ofReduxViewer. This is pretty bad for Flipper performance, with re-renders spending 300-500 ms just runningbuildRow:This PR uses the new Flipper 0.46 feature of generating
copyTextlazily by passing a function instead of a string, so that now re-renders take very little CPU time:This PR also has some changes to
yarn.lock- since the real latest version of Flipper is 0.46, I updated theflipperdependency in the lockfile to 0.46.