question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Requestbody x-www-form-urlencoded is not properly rendered

See original GitHub issue

Q&A (please complete the following information)

  • OS: windows
  • Browser: chrome
  • Version: 67
  • Method of installation: dist
  • Swagger-UI version: 3.17.0
  • Swagger/OpenAPI version: OpenAPI 3.0

Content & configuration

Swagger/OpenAPI definition:

     requestBody:
       description: user info to be filled
       content:
         application/x-www-form-urlencoded:
           schema:
             type: object
             required:
               - username
               - name
             properties:
               username:
                 type: string
                 description: user identity
               name:
                 type: string
                 description: user name
               phone_number:
                 type: string
                 pattern: '/\d{11}/'
                 description: phone number

_20180613215633 Swagger-UI configuration options:

SwaggerUI({
  // your config options here
})
?yourQueryStringConfig

Is your feature request related to a problem?

  • property descriptions are not shown
  • required properties are not starred
  • required properties checking, string regex pattern checking is not performed when try swagger client

However, parameters are ideally shown. There should be no much difference between parameters and body form data.

Describe the solution you’d like

Describe alternatives you’ve considered

Additional context

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:21 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
shockeycommented, Aug 16, 2018

This has been prioritized, and will be fixed shortly 😄

2reactions
bestmike007commented, Jul 12, 2018
Read more comments on GitHub >

github_iconTop Results From Across the Web

application/x-www-form-urlencoded request paramete...
It is working properly in Apigee edge Spec section. ... application/x-www-form-urlencoded request body parameters are not getting rendered ...
Read more >
anyOf in OAS 3.0 for requestBody that is url encoded form ...
"anyOf" in the open APi specs does not render any useful inputs to the fields/elements in the requestBody. The generated curl request takes ......
Read more >
request - Cypress Documentation
A request body to be sent in the request. Cypress sets the Accepts request header and serializes the response body by the encoding...
Read more >
API Reference - Express 4.x
toString() may fail in multiple ways, for example foo may not be there or may not ... of the raw request body and...
Read more >
Scripting API: Networking.UnityWebRequest.Post - Unity
Note: Many server backend languages do not properly handle POST requests with Content-Type headers set to encoding others than application/x-www-form-urlencoded ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found