Skip to content

Type name matching does not seem to follow case sensitivity settings #947

@glopesdev

Description

@glopesdev

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions