Improvements to web api experience around OpenAPI and API Explorer

[pranavkm]

An umbrella issue to track Swagger / OpenAPI work:

• As an HTTP API developer using Open API to enable integration, my APIs include an opinionated convention of ensuring operationId attributes are created for each Web API controller method #27591
• Enable OpenAPI analyzer by default in API apps
• Bugs / improvements:
  • Media type application/problem+json lost in combination with ProducesAttribute
  • ProducesResponseType(typeof(void), ...) causes ApiExplorer to indicate the return type is ProblemDetails
  • Identify if any additional work is pending in ProblemDetails is not returned for 404NotFound and 500Exception
  • Api.Analyzers not recognizing methods from a Base Class
  • Create and include an analyzer that validates action method return types match the declared ActionResult
  • API analyzers should support undeclared 200 status codes
  • [ ] Discriminated unions

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[jeremyVignelles]

Would #28060 fit here ?

[dodyg]

Will ApiExplorer support all the endpoints created via Houdini?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.