Support body parameters

[come-nc]

Hello,

I’m not exactly sure how to decide/detect this, but currently all parameters get documented as in query: "in": "query",

While in our case we expect those in the JSON body of the PUT.
This is a problem when using tools to generate documentation based on the openapi.json file.

[provokateurin]

We also need this to fix a few problems. If parameter is a union type then we can end up with a broken spec (e.g. string and array, but for array the name needs to have [] at the end which).
So basically whenever we detect a non-atomic type we need to switch all parameters to be in the body to be sure that it will work.
A different solution using content in parameters was something I tried with #22, but that still doesn't solve the array name problem and didn't work anyway.

[provokateurin]

I hope I can put some work into this soonish as it also stops people from using type aliases for parameter types

[provokateurin]

Instead of making a flag to turn all parameters into body parameters all the time we could use the new attribute for it to change it for single endpoints/controllers.