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.

OAS 3.0: Request body is uneditable during try-it-out

See original GitHub issue

Swagger UI version: commit a1ce0e7 (ft/oas3 branch)

Looks like it’s not currently possible to edit the request body when trying out a particular operation:

1

Spec:

{
  "openapi": "3.0.0",
  "info": {
    "title": "Test",
    "version": "1.0.0"
  },
  "paths": {
    "/test": {
      "post": {
        "requestBody": {
          "content": {
            "application/json": {
              "schema": {
                "type": "object",
                "properties": {
                  "prop": {
                    "type": "string"
                  }
                }
              }
            }
          }
        },
        "responses": {
          "default": {
            "description": "A response"
          }
        }
      }
    }
  }
}

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
shockeycommented, Jul 26, 2017

I just pushed a commit that disables all Try It Out buttons when viewing an OAS3 spec. It includes a styling fix for the Parameters tab bar, that was causing some height issues when viewing callbacks.


Things that haven’t changed in structure or semantics from Swagger 2.0 will still work in Try It Out, but I’d really recommend waiting until we officially support it. I promise there are subtle bugs that will cause pain, if you try to use the Swagger 2 request constructor with OAS3 😄

0reactions
shockeycommented, Aug 10, 2017

Closing; #3338 will track this feature being implemented.

Read more comments on GitHub >

github_iconTop Results From Across the Web

OpenAPI Specification - Version 3.0.3 - Swagger
It is RECOMMENDED that the root OpenAPI document be named: openapi.json or openapi.yaml . Data Types. Primitive data types in the OAS are...
Read more >
OpenAPI Specification v3.0.3 | Introduction, Definitions, & More
The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for HTTP APIs.
Read more >
Swagger openApi Spec 3.0 - DELETE operation
No, you cannot use the OpenAPI 3.0 Specification and Swagger tools to implement DELETE requests with a request body.
Read more >
Getting started tutorial: Using Stoplight Studio to create an ...
For more on the philosophy of not getting lost in the syntactical details ... Stoplight Studio creates an OpenAPI (OAS) specification file ...
Read more >
There's No Reason to Write OpenAPI By Hand
Some languages do not have any support for annotations, and they achieve ... (define pet-request (json-request "Pet Request Body" ($pet))).
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