-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Core Data: Forward resolvers for pagination selectors #71304
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
Conversation
|
Size Change: +27 B (0%) Total Size: 1.92 MB
ℹ️ View Unchanged
|
tyxla
left a comment
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.
Nice one 👍 Works as expected ✅
Thanks @Mamaduka 🙌
|
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. |
|
Thanks, @tyxla! |
What?
Addresses #55164 (comment).
Calling the
getEntityRecordsTotalItemsorgetEntityRecordsTotalPageswill now trigger a matching entity records resolution and return data. Allowing use for pagination selectors without the need to callgetEntityRecordsexplicitly.Testing Instructions
wp.data.select( 'core' ).getEntityRecordsTotalItems( 'postType', 'post' ).Testing Instructions for Keyboard
Same.
Screenshot