-
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
Block Directory: Memoize store selectors #63346
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: +25 B (0%) Total Size: 1.75 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.
Yeah, I think they were not memoized because it was previously impossible for registry selectors.
Nice 👍 |
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
What?
PR adds memoization to the
getNewBlockTypes
andgetUnusedBlockTypes
block directory store selectors.Why?
This is a follow-up to #57888. It prevents selectors from returning different values when called with the same state.
There were no
useSelect
warnings in the editor because of how these selectors are called in components. ThemapSelect
directly returns values, which satisfies shallow equality.gutenberg/packages/block-directory/src/plugins/installed-blocks-pre-publish-panel/index.js
Lines 19 to 22 in 4f706f1
Testing Instructions
The feature has e2e test coverage.
Testing Instructions for Keyboard
Same.
Screenshots or screencast