Skip to content

Request body x-www-form-urlencoded displayed as JSON #4345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mikebywater opened this issue Mar 19, 2018 · 2 comments
Closed

Request body x-www-form-urlencoded displayed as JSON #4345

mikebywater opened this issue Mar 19, 2018 · 2 comments

Comments

@mikebywater
Copy link

When documenting a POST request with the OAS3 spec I cannot represent parameters posted in a html style form as before.

Previously you could document parameters you wish to post as in:form but now you can only specify parameters in either header, path, query or cookie everything else has to be specified in the requestBody.

I have set the content type of the requestBody to be application/x-www-form-urlencoded but when clicking "try it now" in the UI it makes the json in the text area editable.

image

I have set up the requestBody as follows

      requestBody:
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                fullname:
                  type: string
            encoding:
              fullname:            # color=red,green,blue
                style: form

I would expect it to look like a form in this example

image

There is a high probability I am being a plonker here, but I cant seem to work out how this should be specified to make it display as a form as it would have in 2.x spec. so this feels like a bug to me.

@webron
Copy link
Contributor

webron commented Mar 19, 2018

This is an unimplemented feature. Follow #3641 for progress.

@lock
Copy link

lock bot commented Jul 2, 2019

Locking due to inactivity.

This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.

If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.

Thanks!

@lock lock bot locked and limited conversation to collaborators Jul 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants