-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List View: unmemo recursive getEnabledClientIdsTree #58525
Conversation
Size Change: +25 B (0%) Total Size: 1.7 MB
ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So many footguns when using when createSelector
😅
Thanks for fixing this one up.
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core SVNIf you're a Core Committer, use this list when committing to
GitHub Merge commitsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 this looks great @ellatrix, nice work fixing up the recursion here! 🎉
What?
This selector is currently very expensive because of the recursive calls to an memoized selector for every block. This should speed up the ListView quite a bit.
Why?
It's at least 10x faster for a large post
This is taking up ~10% of the total time it takes to render the ListView:
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast