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
In v7, for non-edm model, we could replace the default ODataUriResolver by adding our service in the configureAction of the EnableDependencyInjection method.
In v8, I didn't find a way to do this. For edm model, there is the configureServices parameter in the AddRouteComponents method, but I didn't find an equivalent for non-edm model.
The text was updated successfully, but these errors were encountered:
I succeeded with an horrible workaround : I use a resource filter to set the Services in HttpContext.ODataFeature() (cf AspNetCoreODataDependencyInjection).
Thanks @kakone for reporting the issue. In v8 you don't need the ODataUriResolver for routing. What behaviour are you expecting? Does your workaround provide that behaviour? Can you share a PR for us to review?
I need the StringAsEnumResolver because I want to be able to do an OData filter like Summary eq '0' instead of Summary eq 'Freezing'. So, I would like to replace the default ODataUriResolver.
I did a sample here. It works well with my custom StringAsEnumResolverFilterAttribute.
I'm going to try to do a PR.
In v7, for non-edm model, we could replace the default
ODataUriResolver
by adding our service in theconfigureAction
of the EnableDependencyInjection method.In v8, I didn't find a way to do this. For edm model, there is the
configureServices
parameter in the AddRouteComponents method, but I didn't find an equivalent for non-edm model.The text was updated successfully, but these errors were encountered: