Should we support the requestBody?

[ms14981]

In our requestBody.feature, we specifically assert that a GET request should accept a body. However, the OpenApi spec says:

In other cases where the HTTP spec is vague (such as GET, HEAD and DELETE), requestBody is permitted but does not have well-defined semantics and SHOULD be avoided if possible.

See https://swagger.io/specification/#operation-object

Perhaps we shouldn't have this test, or if we don't test the same thing elsewhere, repurpose it to make it into a POST (or other method with a well-defined spec for the request body)?

[ms14981]

TODO - see how straightforward this is to support anyway in the Java generator. If it's not difficult, support it anyway. If it is, it's fine for the Java generator to fail this test.

[ColinEberhardt]

We discussed this recently. The conclusion was:

• while the use of request bodies is somewhat undefined for various HTTP verbs, we should still support it
• for languages / frameworks where it is difficult to do so (e.g. the HTTP library does not permit request bodies for GET requests), we should not support
• this means that we expect some generators to fail this test - which is fine. It is an indication that they do not support a certain capability which is not at all critical