mix OData and REST API controllers - ApiExplorer/OpenAPI issues

[swurzinger]

How can I have both OData controllers and non-OData controllers in the same project without causing conflicts? Some of the issues that arise:

• there's the [ODataIgnored] attribute to exclude controllers from the OData routing conventions, but that would require to be added to every controller. Is there some alternative like a filter/convention/... ?
• OData controllers are included in the OpenAPI documents (swashbuckle, using Microsoft ApiExplorer APIs) and causing issues there. I'm currently excluding them using a IControllerModelConvention which sets controller.ApiExplorer.IsVisible = false for OData controllers.
• ODataOutputFormatter is added to every endpoint, causing various issues for OpenAPI document generation. This results in many ApiResponseFormats to be added to every request, even if they are non-OData endpoints. This happens because Microsoft.AspNetCore.Mvc.ApiExplorer.ApiResponseTypeProvider calls ODataOutputFormatter.GetSupportedContentTypes(contentType, responseType), which can't tell whether it's dealing with an OData endpoint and just returns all configured response types it supports. The OData check only happens in ODataOutputFormatter.CanWriteResult when the response is going to be serialized (but this is irrelevant for ApiExplorer).

What could be a good solution for this, especially the last one?