-
Notifications
You must be signed in to change notification settings - Fork 105
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
PropertyValueTypeMismatchException #37
Comments
Hi @ChinhDuong, |
Hi @ChinhDuong, I created a pre-release package at NuGet.org with the fix for this issue. Many thanks, |
Ok, I'll do it, thank you very much
…On Sun, Jan 20, 2019 at 10:20 PM David Belmont ***@***.***> wrote:
Hi @ChinhDuong <https://github.com/ChinhDuong>,
I created a pre-release package at NuGet.org
<https://www.nuget.org/packages/LambdaExpressionBuilder/2.0.2-beta> with
the fix for this issue.
Would you mind checking that out and leaving a comment here to let me know
if it's working correctly now?
Many thanks,
David
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL3abVAk3XN0E1iOm8hQdECjJQgbuNRSks5vFIk2gaJpZM4Xd8EX>
.
|
I tested the bug on 2.0.2-beta. it is not fixed |
…a nullable property) for good [hopefully].
Hi @ChinhDuong, Good news! I believe I got it right this time (even created a couple of tests specifically for that). I just published a new version yesterday. Would you mind having a look at that? Many thanks, |
I got PropertyValueTypeMismatchException when running following. I use .net 4.5.2. Could anyone help me to resolve it? Thanks in advance
class Person{
public long? Id { get; set; };
}
List people = new List<Person>{
new Person { Id = 1 },
new Person { Id = null },
new Person { Id = 2 },
}
var filter = new Filter<Person>();
long?[] idList = new long? { 1 };
filter.By("Id", Operation.In, idList);
var result = people.Where(filter); // throw PropertyValueTypeMismatchException
The text was updated successfully, but these errors were encountered: