Extra (unnecessary?) type generated when processing url encoded body swagger

[chamons]

Describe the bug

In this PR we found an extra type/class was generated:

Paths14Hl8BdFormsdataurlencodedPetAddPetidPostRequestbodyContentApplicationXWwwFormUrlencodedSchema

This was a minor annoyance for .NET, as we mark it internal, but might be more annoying for other languages.

Swagger
Generated File

Expected behavior
@pakrym and I expected this type to be not added.

[timotheeguerin]

I think is this the same issue as #3668

[pakrym]

I don't think so. In that case, the schema is defined by the customer in the swagger. In this case, it's an artifact of the autorest transformations.

[timotheeguerin]

well it is arguable. In OpenAPI3 there is a schema like that, when converting from swagger -> opeanpi3 it makes this schema and then it reflatten it. but if you are using openapi3 directly then this schema is defined in your specs

[pakrym]

I might be missing something. Can you refer to the openapi specification where it talks about explicitly defining schemas for urlencoded bodies?

[timotheeguerin]

As far as I understand in OpenApi3. You have a single entry for the schema requestbody and then you can define the schema per content type

https://swagger.io/docs/specification/describing-request-body/

paths:
  /survey:
    post:
      requestBody:
        required: true
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                name:          # <!--- form field name
                  type: string
                fav_number:    # <!--- form field name
                  type: integer
              required:
                - name
                - email

[pakrym]

TIL. thank you