Created by: mfmarche
Model naming conforms to the property: modelPropertyNaming, however the parameter naming scheme is currently hardcoded to camelcase. Since the parameter names are closely tied to the model properties names, is maybe desirable to use a similar naming approach.
The parameter naming cannot directly use the modelPropertyNaming since that will cause issues with current generated code, since the modelPropertyNaming currently defaults to "original"
A new property has been created to override this behavior, named "paramPropertyNaming", and its default is set to "camelcase".
This PR likely addresses: https://github.com/OpenAPITools/openapi-generator/issues/8296
PR checklist
- [x ] Read the contribution guidelines.
-
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master,5.1.x,6.0.x -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.