William Cheng

you may want to try the workaround mentioned in https://github.com/OpenAPITools/openapi-generator/issues/8844#issuecomment-789714081

@seanlaff have you tried the `modelPropertyNaming` option? ``` modelPropertyNaming Naming convention for the property: 'camelCase', 'PascalCase', 'snake_case' and 'original', which keeps the original name (Default: camelCase) ```

some generators support the name mapping features: https://github.com/openapitools/openapi-generator/blob/master/docs/customization.md#name-mapping so that one can customize the property naming according to the use cases

i did a test and it works: ``` java -jar modules/openapi-generator-cli/target/openapi-generator-cli.jar generate -g typescript-angular -i https://gist.githubusercontent.com/seanlaff/d2aef0244adeeea95c1396952b28d987/raw/b508eb408d600bdeb39f7088c8e3d6ce184020ac/keywordparams.yaml -o /tmp/tsangular2/ --name-mappings default=default ``` and here is the output ```typescript export interface Pet...

did you also try setting `modelPropertyNaming=original`? e.g. `--additional-properties modelPropertyNaming=original` in CLI

i'm not familiar with https://github.com/OpenAPITools/openapi-generator/commit/2512ea071af34e73dbd9d932b5d95a0bad08ba8d (done in 2019) so not much I can tell you about that change in particular.

UPDATE: i've filed https://github.com/OpenAPITools/openapi-generator/pull/19020 @tdetugny do you mind sharing a spec so that we can use to confirm the change is what you want?

should be fixed by https://github.com/OpenAPITools/openapi-generator/pull/19508

thanks for reporting the issue. I think it's caused by https://github.com/OpenAPITools/openapi-generator/pull/17934 @JFCote can you please take a look? shall we revert the change for the time being?

@mpo-wd if you or anyone would like to contribute a PR or sponsor the fix, please let us know.