Inconsistency in the cURLs generated via the swagger-ui and swagger editor

When creating an API resource with a multipart/form-data file upload parameter, the swagger editor and the swagger-UI generates the cURL commands differently.

Q&A (please complete the following information)

• OS: macOS
• Browser: chrome
• Version: [e.g. 22]
• Method of installation: dist assets
• Swagger-UI version: 3.22.0
• Swagger/OpenAPI version: Swagger 2.0

Example Swagger/OpenAPI definition:

swagger: "2.0"
paths:
  /file:
    post:
      parameters:
        - name: file
          in: formData
          required: true
          type: file
      responses:
        "200":
          description: ""
      x-auth-type: "Application & Application User"
      x-throttling-tier: Unlimited
      consumes:
        - multipart/form-data
info:
  title: test
  version: v1

Describe the bug you're encountering

When an API is created from the swagger file provided, the swagger-UI will generate the cURL as follows
curl -k -X POST "https://host:port/test/v1/file" -H "accept: application/json" -H "Content-Type: multipart/form-data" -H "Authorization: Bearer d779534f-ff49-357f-a9e6-64be590df7e6" -d {"file":{}}

However, the swagger editor generates the cURL in the following format;
curl -X POST "https://host:port/file" -H "accept: application/json" -H "Content-Type: multipart/form-data" -F "file=@image.png;type=image/png"

The swagger-UI presents the file data as -d {"file":{}} where as the swagger editor presents it as -F "file=@image.png;type=image/png"

Reproduce the discrepancy in swagger-ui and the swagger editor using the supplied Swagger 2.0 multipart/form-data definition. Compare the generated cURL for the file parameter, then verify that the completed behavior uses the expected multipart file form syntax consistently.