add check and helpful exception message on inconsistent type situation #12
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
Closed
schmittjoh
added a commit
that referenced
this pull request
Dec 17, 2012
add check and helpful exception message on inconsistent type situation
|
Thanks! |
alcalyn
pushed a commit
to alcalyn/serializer
that referenced
this pull request
May 5, 2016
[doc] fix AccessorOrder documentation
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
follow-up of #10 i try to add a mesage.
not sure if there would be a possibility to detect the mistake earlier - but i think not. i was looking at GraphNavigator too, but thought doing the exception right next to where the error could happen is the most reliable even in case the context is going to be used in different ways later.