dbelmont / ExpressionBuilder

A library that provides a simple way to create lambda expressions to filter lists and database queries.
Apache License 2.0
372 stars 105 forks source link

PropertyValueTypeMismatchException #37

Open ChinhDuong opened 6 years ago

ChinhDuong commented 6 years ago

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

dbelmont commented 5 years ago

Hi @ChinhDuong, Many thanks for using the project. And thanks for finding a bug! 🎉 I'll fix that and get back to you once it's done. Cheers.

dbelmont commented 5 years ago

Hi @ChinhDuong,

I created a pre-release package at NuGet.org 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

ChinhDuong commented 5 years ago

Ok, I'll do it, thank you very much

On Sun, Jan 20, 2019 at 10:20 PM David Belmont notifications@github.com 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 https://github.com/dbelmont/ExpressionBuilder/issues/37#issuecomment-455874980, or mute the thread https://github.com/notifications/unsubscribe-auth/AL3abVAk3XN0E1iOm8hQdECjJQgbuNRSks5vFIk2gaJpZM4Xd8EX .

-- http://db.tt/kUFjeZN

ChinhDuong commented 5 years ago

I tested the bug on 2.0.2-beta. it is not fixed

dbelmont commented 5 years ago

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, David