[OpenApi 3] generated swagger.json doesn't respect InputFormatter

What I want to achieve:

Read a POST body into a raw string in my API method. For that, I’m using an InputFormatter that can transform text/plain request into a string parameter.

Observed results:

The API works fine, but the swagger.json generates a content-type of application/json, which makes swagger-ui send the request with this Content-Type header (which cannot be parsed).

When I set my SchemaType to Swagger2, the Swagger UI can handle the API correctly.

Expected result:

Swagger UI should be able to read raw strings from the input, and the C# client should be able to pass a raw string as the POST request body.

Sample code :

https://github.com/jeremyVignelles/TestNSwagNetCoreApp/tree/feature/openapi-raw-inputformatter

[RicoSuter]

I think you need this: https://github.com/RicoSuter/NSwag/pull/2353

You can copy it into your proj and use it

I hope to merge/finish the pr soon

[acds]

@RicoSuter - Thanks!

As an aside there seem to be some issues with Microsoft.AspNetCore.Mvc.Versioning.Versioning 4.1.0 a switchback to 4.0.0 resolved the issue - but tend to upgrade across the board when I can - albeit staying 3.0 compatible packages just now so avoiding 3.1 dependencies) Error:

System.TypeLoadException: Method 'ApplyAsync' in type 'Microsoft.AspNetCore.Mvc.Routing.ApiVersionMatcherPolicy' from assembly 'Microsoft.AspNetCore.Mvc.Versioning, Version=4.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.

Whist using the [OpenApiBodyParameter("text/plain")] works…it would be more preferable (and ignorance on my part of the implications) if NSwag were somehow able to leverage the Microsoft.AspNetCore.Mvc version of the [Consumes("text/plain")] for compatibly with other libraries - it at least then eases the migration?