Created by: richardwhiuk
Currently a field which matches a Rust keyword e.g. type is rendered as the Rust variable _type in order to produce valid Rust. This is confusing, because a leading underscore indicated an unused variable in Rust code.
Instead we match convention in the Rust community and suffix variables with an _ instead. For fields which begin with a number (e.g. 1234word), we prefix them with param_ to avoid this problem, and avoid being unable to to start with a number.
Rust Server Technical Committee
- @frol
- @farcaller
- @bjgill
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.