OpenApi controller endpoint metadata inheritance inconsistent

[ArwynFr]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When using inheritance with controllers, endpoint metadata attributes are not managed consistently.
For instance, OpenApi will use ProducesResponseTypeAttribute inherited from the parent class, but not EndpointSummaryAttribute nor EndpointDescriptionAttribute.

Expected Behavior

No response

Steps To Reproduce

using Microsoft.AspNetCore.Http.HttpResults;
using Microsoft.AspNetCore.Mvc;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddControllers();
builder.Services.AddOpenApi();

var app = builder.Build();
app.MapOpenApi();

await app.RunAsync();

public abstract class PingControllerBase : ControllerBase
{
    [EndpointSummary("This is base summary.")]
    [EndpointDescription("This is base description.")]
    [ProducesResponseType<ProblemDetails>(StatusCodes.Status404NotFound, "application/problem+json")]
    [HttpGet("/api/base")]
    public abstract Results<Ok, NotFound> ExecuteBase();
}

[ApiController]
public class PingController : PingControllerBase
{
    public override Results<Ok, NotFound> ExecuteBase() => throw new NotImplementedException();

    [EndpointSummary("This is child summary.")]
    [EndpointDescription("This is child description.")]
    [ProducesResponseType<ProblemDetails>(StatusCodes.Status404NotFound, "application/problem+json")]
    [HttpGet("/api/ping")]
    public Results<Ok, NotFound> Execute() => throw new NotImplementedException();
}

v1.json

Exceptions (if any)

No response

.NET Version

9.0.203

Anything else?

Microsoft.AspNetCore.OpenApi v9.0.4

[captainsafia]

This behavior is intentional. The ProducesResponseTypeAttributes predate the summary and description attributed and are processed using conventions and response providers in MVC.

The summary and description attributes are newer and follow the "last one wins" model that endpoint metadata uses.

At the moment, it'd be difficult to make changes in the behavior of either without introducing breaks.

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.