I have a resource which includes certain attributes. These attributes can all be included using the
fields[TYPE] parameter, and they can all be filtered and sorted.
I have some other attributes pertaining to a resource that I would like to include, but due to the way they are stored in the database, it would be impossible for me to support such features on these fields using a query builder as I am currently.
So, I would like to know would it be “atypical” to only support sparse fieldsets, filtering and sorting on only some (not all) attributes returned with a resource? Basically, these attributes will always be returned with the resource no matter what.
Is it much of a “common practice” to implement something like this?