Grace Karina Gonzalez Diaz

thanks for this PR!

related https://github.com/swagger-api/swagger-parser/issues/1205

Hey @aneeshafedo, Thanks for sending us this: I was checking the OpenAPI Specification [3.0.3 ](https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md#operationObject)and this is what it says about requestBodies ``` The request body applicable for this operation....

Hi! @aneeshafedo, we have to also warn in parser that in certain HTTP methods is not recommended to use a requestBody.

Hi @mhammadkassem, thanks for reporting this issue, can you please submit a PR with a failing test that exposes the issue, or a sample project, so we can reproduce.

hi @klokane should x-my-extension have the two dots like this: `x-my-extension:`?

We are looking into it!

Hi, @klokane thanks for pointing this issue into our direction, We have looked into it and due it's an old version of the spec and the complexity of resolving it,...

Double checked, and it's the same complex fix.

@klokane, in the meantime, you could access the `unsupported` in `SwaggerDeserializer::ParseResult` by extending deserializer, e.g. like: ``` public class MySwaggerDeserializer extends SwaggerDeserializer{ @Override public MySwaggerDeserializationResult deserialize(JsonNode rootNode) { MySwaggerDeserializationResult result...