Skip to content

Fix: Support for case sensitive properties#1571

Open
CAPCHIK wants to merge 1 commit into
OData:dev-10.xfrom
CAPCHIK:case-sensetive-properties
Open

Fix: Support for case sensitive properties#1571
CAPCHIK wants to merge 1 commit into
OData:dev-10.xfrom
CAPCHIK:case-sensetive-properties

Conversation

@CAPCHIK
Copy link
Copy Markdown

@CAPCHIK CAPCHIK commented May 7, 2026

Allows to use sensitive fields in CLR according to (Case Sensitivity of Property Names, EntitySets, Singletons and Operations)[https://issues.oasis-open.org/browse/ODATA-1150]

That work starts in !1482, but PR was closed due to my mistake with branches

dev-10.x branch selected for check changes with E2E tests

project has several other places with Expression.Property(expression, property_name_as_string), I check and fix only two cases, which breaks my app

I can continue work on that and cover another Expression.Property usings

Tests PropertyNameCaseSensitive_QueryCollection_WorksAsExpected and PropertyNameCaseSensitive_QueryCollectionWithSelect_WorksAsExpected works correctly without changes to Expression.Property and have been added for covering basic cases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant