Sparse Fieldsets Compliance

[st3xupery]

When specifying particular fields for a resource, the system seems to ignore filtering relationships, including them all regardless of the client's requests. This does not comply with the specification sheet here

If a client requests a restricted set of fields for a given resource type, an endpoint MUST NOT include additional fields in resource objects of that type in its response.

Additionally, the term fields does include relationships as can be seen here

A resource object’s attributes and its relationships are collectively called its “fields”.