odata query options (filter/skip/top/orderby) not included in api explorer

[engenb]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I've tried to configure query options globally, via controller action attribute, the new ODataApiExplorerOptions approach and everything else I can think of. regardless, the only two odata query options that I've ever seen included in the api explorer are select and expand - I'm validating this via swagger.

Expected Behavior

configured query options should be included in openapi / swagger doc

Steps To Reproduce

here is a sample repo that demonstrates the issue

Exceptions (if any)

No response

.NET Version

8.0

Anything else?

I've also noticed the only api doc in swagger is v1 - v2 is excluded for some reason. I have not seen this issue before so not sure if it's related or not.

I'm working on migrating from Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer

[commonsensesoftware]

The ODataApiExplorerOptions have been there a lot time, even in the old Microsoft.AspNetCore.OData.Versioning.ApiExplorer.

There's a lot going on this in this project, but this could be the expected behavior. filter, skip, top, and orderby are all nonsensical for a scalars type (e.g. single entity or complex type). This would be the for any API that returns one result by key. Obviously, entity sets and functions should not be so limited. There's not much sense in including all of the query option noise for options that are either unsupported or will have no effect.

A few other notes:

1. You don't need [ApiController] since you're using OData; in fact, that might cause undesirable side effects
2. You're organizing by namespace, you could:
   a. Drop the V# suffix so that you don't need ControllerName
   b. Use the VersionByNamespaceConvention, which would negate the need for [ApiVersion]

I'll have to pull this down and go through it more, but that may be a few quick hints to try a few other things.