The yaml is using a oneOf schema for the parameterIdent path parameter, allowing it to be either a string or an integer. While this is valid OpenAPI, Oat++ and the C++ code generator struggle with oneOf in path parameters, especially when it comes to generating DTOs or type-safe handlers. The oneOf schema is better suited for request bodies or query parameters where polymorphism is easier to handle.
My recommendations is to get rid of the int type (range:0-65535) and put this into the description of the string type.
The yaml is using a oneOf schema for the parameterIdent path parameter, allowing it to be either a string or an integer. While this is valid OpenAPI, Oat++ and the C++ code generator struggle with oneOf in path parameters, especially when it comes to generating DTOs or type-safe handlers. The oneOf schema is better suited for request bodies or query parameters where polymorphism is easier to handle.
My recommendations is to get rid of the int type (range:0-65535) and put this into the description of the string type.