Unnecessary request body definitions on GET routes

[mnahkies]

I've noticed that many operations include an unnecessary request body definition that is essentially defining an empty schema, on routes that don't accept (to my knowledge at least) a request body. For example GET /v1/accounts:

  /v1/accounts:
    get:
      description: ...
      operationId: GetAccounts
      parameters:
        - ...
      requestBody:
        content:
          application/x-www-form-urlencoded:
            encoding: {}
            schema:
              additionalProperties: false
              properties: {}
              type: object
        required: false

This is a bit annoying in terms of code generation, so I'm curious as to the motivation here, and whether these could be removed?

[jar-stripe]

Hi @mnahkies , thanks for reporting. We're investigating and will get back to you as soon as we can!

[jar-stripe]

Hi @mnahkies sorry for the delay! It looks like we do that in order to support functionality within https://github.com/stripe/stripe-mock. We added your request to remove them to our backlog, but for now this is working as expected.

I'll leave this issue open to keep it in our radar, or if anyone else in the community would like to chime in or give it a thumbs up. Thanks again for reporting it!