Add support for empty to-one relationship according to JSON API v1.0 #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| NewsFeedPostResource *testPost = jsonAPI.resource; | ||
|
|
||
| XCTAssertNil(testPost.publisher, @"Test post's attachments should not be nil"); |
There was a problem hiding this comment.
Small copy-and-paste error: the description should read Test post's publisher should be nil.
|
Looks good and useful to me. I think we should include it. |
|
@joshdholtz ping |
|
@RafaelKayumov Thanks for the ping 😊 Merging and stuff |
joshdholtz
pushed a commit
that referenced
this pull request
Jan 12, 2016
Add support for empty to-one relationship according to JSON API v1.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Example from spec here: http://jsonapi.org/format/#fetching-relationships-responses
Tests also added