Is SmartDocs susceptible to the same limitation that OpenAPI has with operation overloading?

[#1]

Is SmartDocs susceptible to the same limitation that OpenAPI has with operation overloading? Refer to OpenAPI issue #146 for details.

For example, an API has two operations:

POST /to/some/collection

Content-Type: application/vnd.example.com.aaa+json

and

POST /to/some/collection

Content-Type: application/vnd.example.com.bbb+json

to overload the endpoint with different resource representations in the request body (the same would be for GET and Accept headers). Another example is the GitHub APIs which use application/vnd.github media types.

Open API 2.0 can't express this - one can only specify one model schema for the request body. Can SmartDocs do this? (We're just starting out with Apigee and have not gotten to the point of defining our API proxies or importing an Open API doc.). This might be a Developer Portal question...

thanks