You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A resource object MAY contain any of these top-level members:
attributes: an attributes object representing some of the resource’s data.
relationships: a relationships object describing relationships between the resource and other JSON:API resources.
links: a links object containing links related to the resource.
meta: a meta object containing non-standard meta-information about a resource that can not be represented as an attribute or relationship.
Ideally, there would be per-View configuration options allowing for exclusion from the returned JSON object. Patterns similar to the remove_links? functionality could be used to conditionally exclude these resource members.
The text was updated successfully, but these errors were encountered:
I imagine the idea is to omit a certain property when it is empty (i.e. unused), or is the goal to sometimes remove populated properties in the response payload?
The goal is to remove populated properties to reduce payload size. For example, removing links from nested objects in an index query but maintaining links at the top level for pagination and such.
Borrowing from the JSON:API Document Resource Objects:
Ideally, there would be per-View configuration options allowing for exclusion from the returned JSON object. Patterns similar to the
remove_links?
functionality could be used to conditionally exclude these resource members.The text was updated successfully, but these errors were encountered: