Sparse Fieldsets behavior changed between v4 and v5 #653
Description
Not necessarily a bug, just an undocumented change so should be alerted to in the upgrade guide as it caused us some grief.
In v4, the behavior was that included relation paths were implied to be included in any sparse fieldsets that are sent but in v5, the relations must be sent in the fieldsets by the client.
For instance, a request like this GET /v1/events?include=resource&fields[events]=id would still result in the resource relation still being returned in the response in v4 even though it's not in the fields parameter for events, whereas it would not in v5.