Exclusion of 'id' and 'type' properties upon request

[merkys]

The specification allows exclusion of id and type properties upon request. Although having no "special" properties sounds nice, JSON response without id and type is invalid according to JSON API specification. Moreover, I cannot think of a use case when the output without idand type would be beneficial. Shall we define id and type attributes as mandatory regardless the value of response_fields?

[rartino]

Oh, right, good point.

Given that we now have very few 'default' fields, I've been thinking about changing the definition of response_fields to be "which non-default fields do you want to be included" and thus provide no mechanism of avoiding any default ones. Then id and type wouldn't need any special treatment. And I think from a user perspective this would be nicer.

[merkys]

Sounds great. It should really be more intuitive.