You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I would expect it to look like a form in this example
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.
The text was updated successfully, but these errors were encountered:
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.
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.
I have set up the requestBody as follows
I would expect it to look like a form in this example
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.
The text was updated successfully, but these errors were encountered: