-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add include
query parameter and be more explicit about top-level included
#219
Add include
query parameter and be more explicit about top-level included
#219
Conversation
Be more specific about the top-level `included` field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @CasperWA for putting this down! To me the PR seems to express all the requirements that I remember from our previous Web meeting, and it reflects how I would (personally) implement the JSON API specification. I've left just a couple of remarks.
Co-Authored-By: Andrius Merkys <andrius.merkys@gmail.com>
Co-Authored-By: Andrius Merkys <andrius.merkys@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before merging, I would like to hear a consideration from @rartino, @fawzi, @sauliusg or @giovannipizzi concerning the inclusion of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made a comment and a suggestion below
Co-Authored-By: Rickard Armiento <gitcommits@armiento.net>
Closes #212
Closes #183