Webapi: [feature/netcore] Can't find how to set EnableCaseInsensitive, EnableUnqualifiedNameCall and EnableEnumPrefixFree in 7.0.0 Beta 2
In the documentation it is stated that EnableCaseInsensitive, EnableUnqualifiedNameCall and EnableEnumPrefixFree can be used to modify the OData behaviour on case, unqualified nam and enums without prefixes. But I can't find these in 7.0.0 beta 2 (Well I can actually find EnableCaseInsensitive, but not how to activate it)? Is this supposed to be like this, or have I missed something obvious and simple?
dozer75
All 9 comments
I also met the issue today, after finished a function and would like to use EnableUnqualifiedNameCall, but couldn't find it. Does anyone know these methods in which namespace with version 7.0.0 beta2?
Julian-Chu
on 27 Mar 2018
For enable unqualified name call, register custom resolver Microsoft.OData.UriParser.UnqualifiedODataUriResolver
C#
builder.MapODataServiceRoute(routeName, prefix, containerBuilder =>
containerBuilder.AddService(ServiceLifetime.Singleton, sp => model)
.AddService(ServiceLifetime.Singleton, sp =>DefaultRouteConventions(routeName, builder))
.AddService<ODataUriResolver>(ServiceLifetime.Singleton, sp => new UnqualifiedODataUriResolver { EnableCaseInsensitive =true })
);
For enable enum prefix free, use resolver Microsoft.OData.UriParser.StringAsEnumResolver.
If you need combine two options, Microsoft.AspNetCore.OData contains class UnqualifiedCallAndEnumPrefixFreeResolver. I don't understood why this class internal.
genusP
on 28 Mar 2018
@genusP Thanks, I'll take a look i this solves my issues!
dozer75
on 29 Mar 2018
Tested now and it seems to work, the documentation should reflect this since this is a change from previous implementation.
The class UnqualifiedCallAndEnumPrefixFreeResolver should definitely be public, for now I copied it into my own project.
dozer75
on 29 Mar 2018
@xuzhg, please make class UnqualifiedCallAndEnumPrefixFreeResolver as public
genusP
on 29 Mar 2018
PR #1324 merged
genusP
on 30 Mar 2018
Thanks!
dozer75
on 30 Mar 2018
@genusP How to let the OData Client Generator know the right namespace when using your code? Now it set's the Default.{action}.
1Jesper1
on 5 Feb 2019
@1Jesper1 Sorry, I don't use this library and can`t help you.
genusP
on 5 Feb 2019
Related issues
khodaie
路
4Comments
johnhzhu
路
4Comments
IgorWolbers
路
3Comments
suadev
路
3Comments
abkmr
路
3Comments
Most helpful comment
For enable unqualified name call, register custom resolver Microsoft.OData.UriParser.UnqualifiedODataUriResolver
C# builder.MapODataServiceRoute(routeName, prefix, containerBuilder => containerBuilder.AddService(ServiceLifetime.Singleton, sp => model) .AddService(ServiceLifetime.Singleton, sp =>DefaultRouteConventions(routeName, builder)) .AddService<ODataUriResolver>(ServiceLifetime.Singleton, sp => new UnqualifiedODataUriResolver { EnableCaseInsensitive =true }) );For enable enum prefix free, use resolver Microsoft.OData.UriParser.StringAsEnumResolver.
If you need combine two options, Microsoft.AspNetCore.OData contains class UnqualifiedCallAndEnumPrefixFreeResolver. I don't understood why this class internal.