Bug Report Checklist
Description
My model get a field called OS-EXT-SRV-ATTR which generate code like:
@JsonProperty("OS-EXT-SRV-ATTR")
private ExtServerAttr OS_EXT_SRV_ATTR;
/**
* Get OS_EXT_SRV_ATTR
* @return OS_EXT_SRV_ATTR
*/
@ApiModelProperty(value = "")
@Valid
public ExtServerAttr getOSEXTSRVATTR() {
return OS_EXT_SRV_ATTR;
}
public void setOSEXTSRVATTR(ExtServerAttr OS_EXT_SRV_ATTR) {
this.OS_EXT_SRV_ATTR = OS_EXT_SRV_ATTR;
}
After serialize with jackson we will get two fields in the result: OS_EXT_SRV_ATTR and osextsrvattr. This is a expected behaviour for jackson, see FasterXML/jackson-databind#1609 . But it's definitely not ideal for my app.
openapi-generator version
I use openapi-generator-maven-plugin 3.3.4, but I tried the latest 4.2.3, no help.
OpenAPI declaration file content or url
Command line used for generation
Steps to reproduce
Related issues/PRs
Suggest a fix
I think the idea behaviour is to seriliaze the field as-is in the yaml model declaration.
Bug Report Checklist
Description
My model get a field called
OS-EXT-SRV-ATTRwhich generate code like:After serialize with jackson we will get two fields in the result:
OS_EXT_SRV_ATTRandosextsrvattr. This is a expected behaviour for jackson, see FasterXML/jackson-databind#1609 . But it's definitely not ideal for my app.openapi-generator version
I use
openapi-generator-maven-plugin3.3.4, but I tried the latest 4.2.3, no help.OpenAPI declaration file content or url
Command line used for generation
Steps to reproduce
Related issues/PRs
Suggest a fix
I think the idea behaviour is to seriliaze the field as-is in the yaml model declaration.