Hello,
I was playing with oatpp1.3.0 trying to fill an ENDPOINT_INFO macro for an endpoint expecting a binary file input as request body (to upload pictures).

I found this issue (47) which helped me fix my lack of documentation :

"requestBody": {
    "required": true,
    "content": {
        "image/png": {
            "schema": {
                "type": "string",
                "format": "binary"
            }
        }
    }
},

However it made me also wonder : why is the classe Binary located inside the oatpp::swagger namespace instead of the oatpp::data::mapping::type namespace (or oatpp::data::type in oatpp1.4.0) like any other OATPP types?

Thank you in advance for any clues about why this is as it is.