Swagger UI - 使用 Microsoft.AspNet.WebApi.Versioning 时的 Web API 版本控制

Jak*_*sky 1 c# asp.net-web-api swagger swagger-ui

我们在Swagger项目中使用Web API 2。我的问题是,当Microsoft.AspNet.WebApi.Versioning应用如下:

在此处输入图片说明

扬鞭UI被忽略的事实是,现在我在的API,它需要提供具有版本。

我看了几个例子,但似乎没有一个能以令人满意的方式解决这个问题。

如何强制 Swagger 让我添加 API 版本或仅将版本号自动添加到 URL?

到目前为止的 Swagger 配置:

GlobalConfiguration.Configuration
                .EnableSwagger(c =>
                {

                    c.SingleApiVersion("v1", "MoovShack.ServerApi");

                    // If your API has multiple versions, use "MultipleApiVersions" instead of "SingleApiVersion".
                    // In this case, you must provide a lambda that tells Swashbuckle which actions should be
                    // included in the docs for a given API version. Like "SingleApiVersion", each call to "Version"
                    // returns an "Info" builder so you can provide additional metadata per API version.
                    //
                    //c.MultipleApiVersions(
                    //    (apiDesc, targetApiVersion) => ResolveVersionSupportByRouteConstraint(apiDesc, targetApiVersion),
                    //    (vc) =>
                    //    {
                    //        vc.Version("v2", "Swashbuckle Dummy API V2");
                    //        vc.Version("v1", "Swashbuckle Dummy API V1");
                    //    });

                    c.OperationFilter<MoovShackTokenHeaderParameter>();
                })
                .EnableSwaggerUi(c =>
                {

                    // If your API has multiple versions and you've applied the MultipleApiVersions setting
                    // as described above, you can also enable a select box in the swagger-ui, that displays
                    // a discovery URL for each version. This provides a convenient way for users to browse documentation
                    // for different API versions.
                    //
                    //c.EnableDiscoveryUrlSelector();

                });
Run Code Online (Sandbox Code Playgroud)

您可以看到到目前为止 MultipleApiVersions 被禁用 - 有一个很好的理由,因为它不会产生任何结果。特别是因为我不确定“ ResolveVersionSupportByRouteConstraint ”应该做什么。

我还读到“ EnableDiscoveryUrlSelector ”有某种影响,但我也不确定这是否适用于我的情况。当我启用它时,什么也没发生。

Moh*_*reh 5

我们在我们的项目中像这样使用它并且swagger识别它并且它看起来很好

[ApiVersion( "1.0" )]
[Route("api/v{version:apiVersion}/[controller]")]  
public class SomeControlelr: Controller{
    [HttpGet("", Name = "Someaction"), MapToApiVersion("1.0")]
    public async Task<IActionResult> SomeAction(string someParameter)
Run Code Online (Sandbox Code Playgroud)

  • 否,因为版本的解析取决于您从组合框中选择的版本。按照此示例:https://github.com/Microsoft/aspnet-api-versioning/tree/master/samples/aspnetcore/SwaggerSample (4认同)