Repository navigation
Type name matching does not seem to follow case sensitivity settings #947
Description
Currently migrating from the old System.Linq.Dynamic to System.Linq.Dynamic.Core and found out that case-sensitivity does not seem to be applied the same way to type conversions. For example, the below parse statement will fail:
var expression = DynamicExpressionParser.ParseLambda(typeof(object), null, "int16(5)");with the message "No applicable method 'int16' exists in type 'Object'".
In the old System.Linq.Dynamic this script used to work, and from exploring this new library it looks like the default should be to support case-insensitive matching as well.
I checked that method and property name matching seems to be case-insensitive, but for some reason type name matching seems to be case-sensitive so I thought to raise this issue.
Activity
StefH commentedon Jun 27, 2026
@glopesdev
I see your issue, but this project follows some different rules:
int16)StefH commentedon Jun 27, 2026
#985
glopesdev commentedon Jun 27, 2026
@StefH understood. Although, in that case, wouldn't it be better to simply make the whole library case-insensitive?
I feel it might be easier to have a consistent set of expectations, rather than having types behaving differently from methods.