Update docs for JSONAPI relationship links#1935
Update docs for JSONAPI relationship links#1935ksamc wants to merge 1 commit intorails-api:masterfrom
Conversation
|
@ksamc, thanks for your PR! By analyzing the annotation information on this pull request, we identified @vasilakisfil to be a potential reviewer |
|
Interesting! I didn't know this method (#1710) at all and I was fixing this issue from the ember's side in a serializer. Looks good to me! |
| ``` | ||
|
|
||
| This will resilt in (example is in jsonapi adapter): | ||
| This will result in (example is in jsonapi adapter): |
| ``` | ||
|
|
||
| This will resilt in (example is in jsonapi adapter): | ||
| This will result in (example is in jsonapi adapter): |
| #more on: https://github.com/rails-api/active_model_serializers/issues/1325 | ||
| def microposts | ||
| object.microposts.loaded ? object.microposts : object.microposts.none | ||
| include_data false |
There was a problem hiding this comment.
For this specific comment, I think it is no longer needed. include_data false is already documented elsewhere as avoiding the N+1/loading the data.
That said, we should probably rework this section. It's totally valid to have both data and links, so there's really no inherent reason to have include_data false in the documentation example in the first place. We're just talking about link generation here.
Instead, I'd add a section below this (or elsewhere) on conditionally including data, how and why one would do this. @ksamc any interest in adding this documentation, based on the explanation in #1931? Otherwise I will submit a separate PR.
There was a problem hiding this comment.
@richmolj I would say the opposite is more often: if you add links you probably don't include the relationship.
I would suggest to merge this request and you can start a new one about conditionally adding data (probably in another section of the wiki)
|
Please commit these changes because I almost losed my mind. |
5 participants
Purpose
Fixes small typos and updated the docs on relationship links for JSONAPI.
Changes
Removed the 'data' key in the serialized relationship. Including it according to the current docs leads to unexpected behavior when using it with libraries like Ember Data.
This method returns an empty array if the relationship is not loaded even though they might exist. Passing an empty array as data tells clients that there are no existing relationships.
Instead data should not be sent at all so that the client uses the given nested resource link to fetch them.
Caveats
Related GitHub issues
Additional helpful information