-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Refactor InserterTabs to use children and remove re-memoizing #61295
Conversation
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 If 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. |
Size Change: +151 B (+0.01%) Total Size: 1.74 MB
ℹ️ View Unchanged
|
const blocksTab = useMemo( | ||
() => ( | ||
const blocksTab = useMemo( () => { | ||
if ( selectedTab !== 'blocks' ) { |
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.
I think this will make the tabs less performant, because we'll need to re-run this code every time the selected tab changes. It would be better to execute the code once and have it cached until we need to change it for another reason.
I pushed a change that removes the |
Flaky tests detected in 4483d6a. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8922376366
|
The inserter performance results are consistently lower with the Checking the performance results from our separate commits, the |
@scruffian - while the memos do run more often with the
|
I'm running the tests again locally between the two and mostly getting better results without the |
We also discovered that the media and patterns tab were both being re-memoised because |
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.
This is looking good now, thanks
This branch:
trunk
|
What?
Follow-up to #61108, which impacted the Inserter Search performance
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast