feat: add per-type API transformer sparse fieldsets - #10285
Merged
michalsn merged 2 commits intoJun 12, 2026
Conversation
michalsn
added
enhancement
datamweb
reviewed
Jun 8, 2026
datamweb
approved these changes
Jun 9, 2026
paulbalandan
approved these changes
Jun 11, 2026
Member
Author
|
Thank you for the reviews! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This PR adds per-type sparse fieldsets for API transformers via
fields[<type>].Transformers can opt in by defining
$resourceType, allowing nested resources to apply their own field filters without inheriting the rootfieldsparameter.Ref: #10278 (comment)
Checklist: