Problem with describing reponse codes in minimal api

[msmolka]

Problem with describing reponse codes in minimal api

[msmolka]

Probably not directly. I’ve seen example with WithOpenApi, but I know I cannot use it here. That’s why I’m asking. But I think it is not right place.

[commonsensesoftware]

Is this specific to API Versioning? This appears to be general in nature with respect to using OpenAPI in Minimal APIs. I recommend starting with the OpenAPI Support in Minimal APIs. Pairing up XML Comments is a specific feature of Swashbuckle. I'm not sure if it supports that in Minimal APIs. If you have specific questions about API Versioning withing these contexts, I'm happy to answer them.

[commonsensesoftware]

WithOpenAPI just attaches the OpenApiOperation as metadata. You should be able to configure the information directly or with one of the many specialized extension method (though I'm not sure there is one for this specific case).

As it relates to API Versioning, you can use all of the provided APIs, but you need to be careful if interleave versions and you want OpenAPI support on a Minimal API. The current design only support attaching a single OpenApiOperation, which can produce the wrong results. I've gone through the scenario with the ASP.NET team, but it doesn't look like we will see that enhancement in .NET 8. The easiest way to avoid that problem is to have a single Minimal API (action method) defined per route+version combination (e.g. do not interleave). Everything else should behave normally. If you're hitting a wall here, I can try to help out.

In terms of XML Comments, API Versioning doesn't get use them or involve them in any way.