Relationship serializer class option #94
Closed
Conversation
This file contains hidden or 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
|
Cool, I think I'm good with this architecture. There are a bunch of spelling mistakes all over, can you do a pass over? |
|
I see the one for the constant. Anything else? |
|
|
added 3 commits
December 9, 2016 16:07
Add new option when declaring a relationship in the serializer that specifies the serializer class. This will take precedence over looking up the serializer based on the given object to serialize.
|
Fixed these two, plus added a link in the README for the new section. |
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.
Add new
serializeroption when declaring a relationship. This is helpful when there are shared relationship serializers that are outside of lookup namespace.For instance this serializer project structure: