Code generation bug in parameters required checking

"requestBody" : {
"content" : {
"application/x-www-form-urlencoded" : {
"schema" : {
"$ref" : "#/components/schemas/Parameter"
}
}
}
}

...

"components" : {
"schemas" : {
"Parameter" : {
"type" : "object",
"required" : [ "id" ],
"properties" : {
"id" : {
"type" : "string",
"description" : "Application Name that you have configured in your Enterprise Account when configuring the integration options."
}
}
}
}

}

Tested in context of : "library" set to "okhttp-gson".

1. Even "id" is set required in specification, but such parameter is taken as optional and no validation is done prior a call in generated "api class".
2. I would like to suggest if it could be used even as option to use entire object in call to avoid that code rewrite for new added optional parameter.

Start with the okhttp-gson generator entry points and the generated API class described in the report, then reproduce the required-field behavior using the supplied OpenAPI schema. Check how the required id in Parameter is represented before a call; done means the generated client handles that required field as specified, with the object-based call option clarified or implemented if in scope.