Microsoft.AspNetCore.OpenApi: Support API versioning (required for Swashbuckle feature parity) about aspnetcore HOT 2 OPEN

@josundt Thanks for filling this issue!

Things actually work the other way around with respect to API versioning + OpenAPI in ASP.NET Core.

The Asp.Versioning.Mvc.ApiExplorer package that you referenced above integrates with ASP.NET Core's API explorer implementation. API explorer allows frameworks to expose an implementation of IApiDescriptionProvider that consumers can inspect to generate OpenAPI documentation.

All OpenAPI implementations in the ASP.NET ecosystem depend on API Explorer (NSwag, Swashbuckle, and our own Microsoft.AspNetCore.OpenApi) and can pick up the additional metadata that Asp.Versioning adds to the ApiExplorer interfaces in order to access versioning information.

With regard to how the new Microsoft.AspNetCore.OpenApi package integrates with Asp.Versioning, check out this PR on the eShop repo for an example of what the delta between the two implementations is.

Have you tried using Microsoft.AspNetCore.OpenApi in a project alongside Asp.Versioning and ran into issues?

from aspnetcore.

Hi @josundt. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

from aspnetcore.