Created by: richardwhiuk
This adds support to Rust Server for query parameters encoded in JSON - e.g.
- name: list-of-strings
in: query
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/StringObject'
There's a small change to the core code to record the content type, and then there's an update to the Rust Server code to support JSON decoding.
Note, no attempt is made to support anything other than JSON query parameters - you can in theory specify an arbitrary mime type here.
This change was contributed by @mirw and reviewed by myself.
Rust Server Technical Committee
- @frol
- @farcaller
- @bjgill
- @paladinzh
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.sh
if 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.