-
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
Block Editor: Don't memoize 'getContentLockingParent' and 'getParentSectionBlock' selectors #65649
Conversation
…ectionBlock' selectors
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.77 MB
ℹ️ View Unchanged
|
So the memoization can be valuable sometimes for selectors that return primitive values, but only if the selector is not great performance wise (compared to checking memoized values). I think for these ones, you're probably right that it's not worth it. |
I think when the selector returns a primitive value, we should follow your advice - measure then optimize. If we notice that the selector performs poorly, then we can look for other solutions like memoization. |
Thanks @Mamaduka, another good find! |
What?
This is similar to #65617.
PR removes memoization for the private
getContentLockingParent
and 'getParentSectionBlock' selectors.Why?
The memoization is not particularly valuable here since both selectors return primitive string values.
Testing Instructions
CI checks should be green.