Created by: cghislai
The openapi specification (v3.0.3 https://swagger.io/specification/#operation-object) specifies that the request body shall be ignored where the RFC7231 method semantics are not clearly defined.
It appears request bodies for DELETE method are used and supported by thirdparty libraries such as angular. This prompted support for it in some generators. However, the petstore test spec does not define any request body, and these features were not tested.
This change includes a request body for the deletePet operation. Since consumers are suggested to ignore it, I thought it would make more sense to provide it in a specification that is used across many generators to ensure none of them would throw an error or fail to compile rather than ignoring it.
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(5.3.0),6.0.x -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.