Is there a way change the Controller's name in the swagger-ui page?

Question

I\'m using Swashbuckle to enable the use of swagger and swagger-ui in my WebApi project.

In the following image you can see two of my controllers shown in the swagger-ui

Answer 1

I tried using venerik's answer, but it still kept the original controller name in the UI along with the new tag that you specify. I also didn't like that you had to add an attribute to every function, so I came up with a solution where you only have to add an attribute to the controller. There are two steps:

Add DisplayNameAttribute on the controller:

[DisplayName("Your New Tag")]
public class YourController : ApiController
{
    // ...
}

Then in the Swagger configuration, you can override the base functionality using the GroupActionsBy function to pull the name that you specified in that attribute:

GlobalConfiguration.Configuration
    .EnableSwagger(c => {

        c.GroupActionsBy(apiDesc => {
            var attr = apiDesc
                .GetControllerAndActionAttributes<DisplayNameAttribute>()
                .FirstOrDefault();

            // use controller name if the attribute isn't specified
            return attr?.DisplayName ?? apiDesc.ControllerName(); 
        });

    })
    .EnableSwaggerUi(c => {
        // your UI config here
    });

ControllerName() is an extension method defined in the Swagger-Net library. If you aren't using that you can also get the controller name from apiDesc.ActionDescriptor.ControllerDescriptor.ControllerName

Answer 2

If one wants to do this at a Controller / Class level, the following is a very useful extract from here

use the [ApiExplorerSettings(GroupName = "Group")] on your controllers

Then in Startup

services.AddSwaggerGen(options =>
{
options.SwaggerDoc(version,
    new Info
    {
        Title = name,
        Version = version
    }
);

options.DocInclusionPredicate((_, api) => !string.IsNullOrWhiteSpace(api.GroupName));

options.TagActionsBy(api => api.GroupName);
});

Also note that

5.0.0-beta of swashbuckle now includes an TagActionsBy overload that supports returning an array of tags. This should allow for the above customizations to be simplified

Answer 3

Version 5 of Swashbuckle supports the following option (to be used in the call to AddSwaggerGen()):

options.TagActionsBy(api => new[] { api.GroupName });

This should be used in combination with the following attribute on your controllers or actions:

[ApiExplorerSettings(GroupName = "...")]

However, by default the group name is used to include the operation in a specific document. So this may lead to unexpected results (depends on your naming of the document in calls to options.SwaggerDoc(name, ...)).

To make it work you may have to add this:

options.DocInclusionPredicate((name, api) => true);

Here, for every operation, name is the name of a document and the group name is available in api.GroupName. To include the operation in the document regardless of its group name, simply return true.

Answer 4

By default if I have a controller called ShippingController then the swagger generated UI with name "Shipping"

I was looking to change the name of my controller to something more friendly or in another language. The best I could find was to use a SwaggerOperation attribute to change the name, but this has the limitation that it is a method level attribute and I dont really want to specify the name on every method.

So, I created a convention class to use with controller Route attribute, that we usually use on our controllers and then have the swagger use that to be the name of the controller. Well you know there is a name property on the attribute but the generated swagger doesnt seem to use it.

STEP 1: Create this class:

When the app starts up it will run this and I will be able to look up the Route attribute on my controllers if they have the attribute specified and then use the name property to change the name of the Controller.

using Microsoft.AspNetCore.Mvc;
using Microsoft.AspNetCore.Mvc.ApplicationModels;

namespace RestServices.Configuration.ConfigInstallers.Conventions
{
    public class ControllerDocumentationConvention : IControllerModelConvention
    {
        void IControllerModelConvention.Apply(ControllerModel controller)
        {
            if (controller == null)
                return;

            foreach (var attribute in controller.Attributes)
            {
                if (attribute.GetType() == typeof(RouteAttribute))
                {
                    var routeAttribute = (RouteAttribute)attribute;
                    if (!string.IsNullOrWhiteSpace(routeAttribute.Name))
                        controller.ControllerName = routeAttribute.Name;
                }
            }

        }
    }
}

STEP 2: Startup.cs:

Modify the StartUp.cs file and in the configure services we need to register our class in the Conventions list. See below:

services.AddControllers(o =>
{
   o.Conventions.Add(new ControllerDocumentationConvention());
});

STEP 3: In each controller add name property in Route Attribute:

[ApiController]
[ApiVersion("1.0")]
[ApiExplorerSettings(IgnoreApi = false, GroupName = "v1")]
[Route("api/Envios/{version:apiVersion}", Name =  "Envios", Order = 1)]
[Produces("application/json")]
public class ShippingController

Now when I run the app and my swagger is generated you can see the controller name is changed to be the same as the text in the route attributes name property.

Answer 5

You can use tags for that. By default Swashbuckle adds a tag with the name of the controller to every operation. You can override that with the SwaggerOperationAttribute. For instance, the next line replaces the default tag, Values, with the tag Test:

public class ValuesController : ApiController
{
    [SwaggerOperation(Tags = new[] { "Test" })]
    public IHttpActionResult Get()
    {
        // ...
    }
}

The Getoperation will now be put in the group Test.

If you want the operation to appear in multiple groups you can add more tags. For instance:

[SwaggerOperation(Tags = new[] { "Test", "Release1" })]

will put the Get operation in the groups Test and Release1.