Closed tobyzerner closed 7 years ago
Thinking about how this would work in the code, at most it would just be an alternative way of specifying the includes/sparse fieldsets. Under the hood, the Document would simply pass these assignments on to the root Element.
Do people see any value in adding this API?
And some further thought leads me to realize that the Document itself has nothing to do with includes and fields — these are indeed directives for the top-level data, so it absolutely makes sense to be setting them on the root Element.
I see no reason to increase the API surface area here.
Since sparse fieldsets and includes are a global concept, ie, they are specified once in the URL and have an effect on all resources in the document:
Does it make sense to be specifying them on Resources/Collections, rather than on the Document itself? eg,