Skip to content
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.

Sign up for GitHub

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

Jump to bottom

EF.Property<T>() should work for navigation properties, also in Include()/ThenInclude() #6412

Closed
divega opened this issue Aug 25, 2016 · 1 comment
Closed

EF.Property<T>() should work for navigation properties, also in Include()/ThenInclude() #6412

divega opened this issue Aug 25, 2016 · 1 comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
2.1.0

Comments

@divega
Copy link
Contributor

divega commented Aug 25, 2016 •
edited
Loading

This is an addition to #3921 which will allow paths of navigation properties to be passed as a string to Include() to work but without strong typing.

This would make the API work uniformly for more query scenarios and also enable specifying the name of a property to traverse more dynamically but without losing strong typing.

Potentially we can make this pattern work for "shadow" navigation properties.
@divega divega added this to the Backlog milestone Aug 26, 2016
@divega divega added the help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. label Aug 26, 2016
@AndriySvyryd AndriySvyryd mentioned this issue Aug 30, 2017
Closed
@ajcvickers ajcvickers added closed-not-needed closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. and removed consider-for-current-release labels Sep 7, 2017
@ajcvickers
Copy link
Member

This is now fixed navigation properties in Include/ThenInclude. We will revisit this if other important cases come up in the future.

@ajcvickers ajcvickers removed the help wanted This issue involves technologies where we are not experts. Expert help would be appreciated. label Sep 9, 2017
@bricelam bricelam modified the milestones: Backlog, 2.1.0 Jan 2, 2018
@ajcvickers ajcvickers modified the milestones: 2.1.0-preview1, 2.1.0 Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
4 participants
@bricelam @divega @ajcvickers @AndriySvyryd