-
-
Notifications
You must be signed in to change notification settings - Fork 158
fix(#425): fetching HasManyThrough returns no includes #427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(#425): fetching HasManyThrough returns no includes #427
Conversation
@@ -0,0 +1,104 @@ | |||
<!DOCTYPE html> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these need to be removed. doc artifacts are only supposed to be created when /p:DocFx=true
and shouldn't be checked in. were these built automatically or were you building the docs intentionally?
{ | ||
Type rightInstancesListType = typeof(List<>).MakeGenericType(hasManyThroughRelation.Type); | ||
PropertyInfo rightPropertyOnLeft = _jsonApiContext.RequestEntity.EntityType.GetProperty(hasManyThroughRelation.InternalRelationshipName); | ||
foreach (var leftInstance in included) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is going to enumerate and materialize the query result set which is not something we should do yet. i'm thinking the work of mapping these values back should be moved to the serializer. looking closer it looks like the problem exists in the DocumentBuilder
and the use of an older api that can't traverse the HasManyThrough relationship.
BUG FIX
Closes issue #425
Replaces pull request #426, which can be ignored and deleted.