Skip to content
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

returning array vs object for an individual resource #99

Open
rhec opened this issue Oct 7, 2014 · 2 comments
Open

returning array vs object for an individual resource #99

rhec opened this issue Oct 7, 2014 · 2 comments

Comments

@rhec
Copy link
Contributor

rhec commented Oct 7, 2014

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?

@GavinJoyce
Copy link
Contributor

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

@ronindesign
Copy link

This should probably be closed since pending discussion has been closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants