RapiDoc doesn't treat complex data as 'application/json' in 'multipart/form-data' request

[glprojetinho2]

Here is a quote from the OpenAPI docs:

If the property is complex, or an array of complex values, the default Content-Type is application/json.

That's not what I'm seeing in this example request:

"/test": {
  "post": {
    "summary": "Tests multipart",
    "operationId": "upload",
    "requestBody": {
      "content": {
        "multipart/form-data": {
          "schema": {
            "type": "string",
            "properties": {
              "shouldBeJson": {
                "type": "object",
                "properties": {}
              }
            }
          }
        }
      },
      "required": true
    },
    "responses": {
      "200": {
        "description": "Success"
      }
    }
  }
}

Adding encoding doesn't work:

"encoding": {
  "metadata": {
    "contentType": "application/json"
  }
}

These requests were made with the help of a minimal actix server that I built to test this:
rapidoc.tar.gz
This gzip file also contains a Swagger-Ui version of the api docs. It has the same problem, but the "encoding trick" works (not completely)
Am I missing something? I'm having a lot of problems with this little thing.

[mrin9]

thanks for reporting and pointing to the spec. I have added this to our task queue .
However at the moment we are in the middle of working for the next version which is bundling RapiDoc in pure ES Module format. This is adding up a lot of manual testing as our tests are not yet automated.
Expect some delay in newly reported issues