HuntJason
commented
1 year ago Using the Convention Model (ODataQueryOptions) as opposed to the Attribute Model ([EnableQueryAttribute]) does not route the command to the controller.
In my opinion, it is preferable to use the Convention Model as the QueryOptions can be applied to an Entity Framework query; returning fewer records between the database and the controller before returning it to the calling client as opposed to returning ALL records from the database and then filtering them in the service prior to returning them to the client.
Steps to replicate: When running the ODataRoutingSample and opening the Swagger UI, execute the api/Accounts endpoint. Putting a breakpoint within the controller method does not get hit.
julealgon
Assemblies affected Which assemblies and versions are known to be affected e.g. ASP.NET Core OData 8.x
Describe the bug A clear and concise description of what the bug is.
Reproduce steps The simplest set of steps to reproduce the issue. If possible, reference a commit that demonstrates the issue.
Data Model Please share your Data model, for example, your C# class.
EDM (CSDL) Model Please share your Edm model, for example, CSDL file. You can send
$metadatato get a CSDL XML content.Request/Response Please share your request Uri, head or the request body Please share your response head, body.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Please share your call stack or any error message Add any other context about the problem here.