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.

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

Solve the 3.0 regression: Cannot use generics w/ interface to construct expression bug #18651

Closed
wants to merge 1 commit into from

Conversation

ocdi
Copy link

@ocdi ocdi commented Oct 30, 2019

This change re-writes an expression to skip over UnaryExpressions where the inner expression is an interface. I am not sure if this is the appropriate way to implement this, however it works for the test case I created. This bug is a blocker on us migrating to 3.x as we use this generic interface, so will be very happy if this is merged.

I have tested and verified these changes on the release/3.0 branch and can make a PR for that instead if that were helpful.

Fixes #17794

@dnfclas
Copy link

dnfclas commented Oct 30, 2019

CLA assistant check
All CLA requirements met.

… wrong property name exception

* Change the EFCore.Relational and EFCore.InMemory TranslatingExpressionVisitors to handle interface conversion and bypass it

Fixes #17794
@smitpatel
Copy link
Contributor

This is incorrect fix. If the interface is unknown and we are in client eval, we need to preserve it.

@ocdi ocdi closed this Oct 31, 2019
@ocdi ocdi deleted the bug/17794 branch November 7, 2019 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3.0 regression: Cannot use generics w/ interface to construct expression
3 participants