-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace ODataUriResolver for non-edm model #422
Comments
I succeeded with an horrible workaround : I use a resource filter to set the |
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 |
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: