Fix instantiation problem in ERRest when the destination entity of a relationship is abstract #520
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
…relationship is abstract This commit fix a problem when the destination entity of a toOne or a toMany relationship is abstract. Instead of trying to create an instance of the abstract class (which causes an error), ERRest will try to create an instance based on the type attribute.
hprange
added a commit
that referenced
this pull request
Dec 9, 2013
Fix instantiation problem in ERRest when the destination entity of a relationship is abstract
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.
This commit fix a problem when the destination entity of a toOne or a toMany relationship is abstract. Instead of trying to create an instance of the abstract class (which causes an error), ERRest will try to create an instance based on the type attribute.