This repository was archived by the owner on Jun 6, 2024. It is now read-only.
Support for polymorphic relationships #367
Open
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
It is desirable to be able to include a collection of resources that may inherit from one type, but have different types. This is both supported by the JSON API spec, and by many front end frameworks that implement it like ember which provides this excellent use case.
The change here is to allow for users to define a type_ attribute on the serialized instance that takes preference over a type defined with the type_ key. This results in no behavior changes for existing functionality, and should be considered backward compatible.
Thank you everyone for you work on this; I am making use of this library and am a big fan.