Core Data: Derive collection totals for unbound queries #64772
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mamaduka
added
[Type] Enhancement
|
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: +7 B (0%) Total Size: 1.78 MB
ℹ️ View Unchanged
|
Mamaduka
force-pushed
the
try/core-data-unbound-query-totals
branch
from
509b34e to
ea3621e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
PR updates the
getEntityRecordsresolver and derives collection totals from returned records. This ensures the total items/page selectors are consistent for all queries.Why?
Unbound queries can't use response header information due to how to fetch all middleware works. It requires the
parseargument to betrue.Testing Instructions
wp.data.select( 'core' ).getEntityRecords( 'postType', 'wp_block', { per_page: -1 } );wp.data.select( 'core' ).getEntityRecordsTotalItems( 'postType', 'wp_block', { per_page: -1 } );Testing Instructions for Keyboard
Same.