You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@lburgazzoli I looked into this in detail. The AllOf classname generation is baked into the Java code that create type names. So, overriding it would require writing a new custom generator written in Java, perhaps inheriting the existing Java generator.
It turns out there is also an open issue in the generator for why these classes are generated. There is a workaround that requires modifying our openapi definitions to move properties from out of allOf and into the root of the outer object, e.g.:
But, the original definition seems to be the way the openapi spec suggests property inheritance should be done. So, I'm not sure whether we should be deviating from the spec and change our model definitions or live with the genreated AllOf class names.
The
ConnectorDeployment
metadata is defined asConnectorDeploymentAllOfMetadata
where tha "AllOf" adds nothing:We should investigate if simpler names are possible, like
ConnectorDeploymentMetadata
The text was updated successfully, but these errors were encountered: