You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The injected ODataUriResolver should have EnableCaseInsensitive default to true
Actual result
The injected ODataUriResolver has EnableCaseInsensitive default to false
Additional detail
Related to OData/AspNetCoreOData#1312, where the call to AddRouteComponents configures an ODataUriResolver with EnableCaseInsensitive set to true but when AddDefaultODataServices is called, it configures an ODataUriResolver with EnableCaseInsensitive set to false. This is not a bug per se, but true is arguably the more appropriate default given the OData standard and in line with the principle of least astonishment.
The text was updated successfully, but these errors were encountered:
OData V4.01 states that services MUST support case-insensitive system query option names specified with or without the $ prefix.
For this reason, we inject a case insensitive
ODataUriResolver
in ASP.NET Core OData:https://github.com/OData/AspNetCoreOData/blob/1368836752963d88e920d9508d94807eb995894b/src/Microsoft.AspNetCore.OData/ODataOptions.cs#L326-L329
For the same reason, we should consider defaulting
EnableCaseInsensitive
to true when initializing a new instance ofODataUriResolver
in ODL:odata.net/src/Microsoft.OData.Core/UriParser/Resolver/ODataUriResolver.cs
Line 24 in 95233fc
Assemblies affected
Expected result
The injected
ODataUriResolver
should haveEnableCaseInsensitive
default totrue
Actual result
The injected
ODataUriResolver
hasEnableCaseInsensitive
default tofalse
Additional detail
Related to OData/AspNetCoreOData#1312, where the call to
AddRouteComponents
configures anODataUriResolver
withEnableCaseInsensitive
set totrue
but whenAddDefaultODataServices
is called, it configures anODataUriResolver
withEnableCaseInsensitive
set to false. This is not a bug per se, buttrue
is arguably the more appropriate default given the OData standard and in line with the principle of least astonishment.The text was updated successfully, but these errors were encountered: