Conflict between TagActionsBy and [SwaggerTag(...)]

[tyler-boyd]

Environment

.NET 7.0
Swashbuckle.AspNetCore: 6.5.0

Issue

Possibly related to #2160

I can use options.TagActionsBy(...) to customize the tag names for an operation.
However, if I also use the [SwaggerTag(...)] attribute on the operation, then it will create a new tag in the swagger tags section using the default name (controller name) and apply the description there, leading to empty tag sections on the swagger UI. This behaviour appears to be due to how AnnotationsDocumentFilter works (it doesn't look at swaggerGenOptions.SwaggerGeneratorOptions.TagsSelector at all).

Ideally, that filter would apply the tag descriptions to the tag specified by TagActionsBy, instead of the default (controller name).

Not a major issue, but it's a bit unfortunate that these two features don't work together.

[cadmaticpgustafsson]

I have the same problem, does anybody know of a workaround? Is it possible to something like a SwaggerSchemaFilter for controllers?

[pablokawan]

Same problem here, im trying to add a description to my controller using SwaggerTag but this implies in a new swagger section