-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Allow For Exclusion of Optional Resource Members #312
Comments
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. |
So is the goal is to omit based on which I wonder if this could also be achieved by adding support for |
Yep exactly. Yeah that seems like a very viable solution. I'll play around with it locally and see what needs to be adjusted as a result. |
This issue has been automatically marked as "stale:discard". We are sorry that we haven't been able to prioritize it yet. |
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: