Zev Spitz

@khmurach This works for me: ```csharp var lst = new List(); var qry = lst.AsQueryable().Where("GivenName.Contains(\"sa\", StringComparison.OrdinalIgnoreCase)"); public class User { public string? GivenName { get; set; } } ``` Visualizing...

@khmurach It seems that .NET Framework 4.5.1 doesn't support this overload of `Contains`:  How would you do this with a strongly-typed query? N.B. The `filter` you are passing into...

@JonathanMagnan Let me clarify. All instance methods are handled by Dynamic LINQ, as are their arguments. You can put an arbitrary expression as an argument to any instance method and...

It's also telling that the documentation describes the parameter for `ContainsKey` as `selector`; this is incorrect. While it's true that `ContainsKey` can contain an arbitrary expression, as in your example...

What does `source.ElementType` return? `source.GetType()`? Are you calling any other LINQ methods to create `source`? Just to confirm, `MemberTypeText` is a field, not a property?

The following: ```csharp using System.ComponentModel.DataAnnotations; using System.Linq.Dynamic.Core; using System.Reflection; IQueryable source = new List().AsQueryable(); source = source.OrderBy("MembershipTypeText"); Console.WriteLine( source.Expression ); public enum MembershipType { Simple, Complex } public class MemberDto...

@StefH Something like this: ```csharp var qry = new List().AsQueryable().Where(x => ((Func)(() => x.LastName + x.FirstName))().Length >0); class Person { public string LastName {get;set;} public string FirstName {get;set;} } ```...

The [documentation](https://dynamic-linq.net/expression-language#operators) suggests this should be possible: > | Category | Expression | Description | > | -- | -- | -- | > | ... | > | Primary...

@JonathanMagnan > While this library tries to support as much as possible, it doesn't support everything such as LINQ method in an expression. The [documentation](https://dynamic-linq.net/expression-language#sequence-operators) suggests that the library does...

AFAICT the primary issue is that `it` already refers to the outer lambda parameter; how should `it` refer to the inner lambda parameter? But one way to resolve this might...