perf(ui): don't return full documents on bulk UI operations #14145
Conversation
This file contains hidden or 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
tak-amboss
requested review from
AlessioGr,
JarrodMFlesch and
jacobsfletch
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Modified bulk operation UI components (PublishMany, UnpublishMany, RestoreMany, DeleteMany, EditMany) to send an empty
selectobject in their API requests, which returns only document IDs instead of full documents.Why
Bulk operations were returning complete document data including all relationships, causing:
The UI only needs document counts for success/error messages, not the full data.
How
Added
select: {}parameter to query strings in all bulk operation components. When the API receives an empty select object, it returns only theidfield.