Fixed missing check for explicit key in Contrib GetaAync() #382
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
| if (!keys.Any()) | ||
| throw new DataException("Get<T> only supports en entity with a [Key] property"); | ||
| var explicitKeys = ExplicitKeyPropertiesCache(type); | ||
| if (keys.Count() > 1 || explicitKeys.Count() > 1) |
There was a problem hiding this comment.
Shouldn't this be if (keys.Count() + explicitKeys.Count() > 1)?
|
Pulling this in as it fixes the one breaking test - I wan to revisit how explicit keys are implemented in general though - we can be much more DRY here with attribute inheritance I think. |
NickCraver
added a commit
that referenced
this pull request
Nov 22, 2015
Fixed missing check for explicit key in Contrib GetaAync()
|
👍 |
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.
No description provided.