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
As I read it the current json-api spec says the api should return a single object when a single resource is requested, rather than an array of length one. RestPack currently returns an array. I can understand holding off on changing this, given there is still open discussion about it, so I wanted to ask if you'd consider a patch to match the current spec. If not, what about considering a patch to remove the pagination metadata from individual resource responses, just to reduce overhead?
The text was updated successfully, but these errors were encountered:
Excluding paging meta data for individual resources would certainly be welcome. I would like to hold off on modifying the default for single resource representation until the liked discussion has completed, although a configuration option would allow us to provide both
As I read it the current json-api spec says the api should return a single object when a single resource is requested, rather than an array of length one. RestPack currently returns an array. I can understand holding off on changing this, given there is still open discussion about it, so I wanted to ask if you'd consider a patch to match the current spec. If not, what about considering a patch to remove the pagination metadata from individual resource responses, just to reduce overhead?
The text was updated successfully, but these errors were encountered: