Request body standardization with multiple content types accepted

I use Autorest and the ModelerFour plugin to generate resource types for the Azure Bicep project. ModelerFour has not been able to process some ARM swagger documents since https://github.com/Azure/autorest/pull/4405; specifically, resources under the Microsoft.Web namespace can no longer be generated because the ARM resource provider can consume the same object structure as either JSON or form data.

Should ModelerFour permit requests with the same structured input over two different content types? I saw that there is a special case to allow operations to consume both XML and JSON but was wondering if a more general solution would be possible.

Before asking the question:

• have you checked the faq, the documentation in the docs folder and couldn’t find the information there
• have you checked existing issues for a similar question?

[timotheeguerin]

It is possible in openapi3 to do, what it means here is that the payload schema is the same but it can be serialized as json or formData. I was just asking on what was m4 behavior before if you know, was it just ignoring the formData type and acting like this was just application/json. As far as I know the generators don’t support different serializion types for the same schema which is why this check is there complaining but we could have the same special case as with xml where if json is specified it takes precendence

[jeskew]

Hey @jeskew can you confirm this PR resolve the issue following the instruction on this comment #4543 (comment)

It does! Thanks for the quick work on this.