Created by: richardwhiuk
Currently if we can't parse an enum, additional properties, or form-encoded parameter to a String, we will return an error of ().
This both doesn't include any detail, and cause a compilation failure, as () doesn't implement Display.
This changes the parse error to String or &'static str (depending on the case) to fix up these issues.
This is breaking because this code could be relied on by a user of this crate.
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.