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

Query: Better exception message when invalid expression in Include #1883

Closed
rowanmiller opened this issue Mar 23, 2015 · 2 comments
Closed

Query: Better exception message when invalid expression in Include #1883

rowanmiller opened this issue Mar 23, 2015 · 2 comments
Assignees
@maumar
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

@rowanmiller
Copy link
Contributor

See this thread #1833
We should provide a clearer error stating that only navigation paths are allowed at the moment
@rowanmiller rowanmiller mentioned this issue Mar 23, 2015
Closed
@rowanmiller rowanmiller added this to the 7.0.0 milestone Mar 23, 2015
@rowanmiller rowanmiller changed the title Better exception message when invalid expression in Include Query: Better exception message when invalid expression in Include Dec 3, 2015
@rowanmiller rowanmiller removed the pri1 label Dec 8, 2015
@rowanmiller rowanmiller modified the milestones: Backlog, 7.0.0 Dec 8, 2015
@smitpatel
Copy link
Contributor

@maumar - What would be current exception message?

@maumar
Copy link
Contributor

maumar commented Aug 15, 2017

Fix for #3910 should address this. New exception is (will double check that the scenario in the bug is affected)

Lambda expression '{includeLambdaExpression}' is not valid for Include/ThenInclude result operator. The expression should represent a property access: 't => t.MyProperty'. Specify lambda parameter explicitly to access navigations on derived types: '(Derived t) => t.MyProperty'. For more information on including related data, see

@maumar maumar self-assigned this Aug 15, 2017
@ajcvickers ajcvickers added 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 propose-close labels Sep 7, 2017
@ajcvickers ajcvickers modified the milestones: 2.1.0, Backlog Sep 7, 2017
@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

@maumar maumar

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
@ajcvickers @smitpatel @maumar @rowanmiller