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

[jblazquez]

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:

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"
          }
        }
      }
    }
  }
}

[webron]

The try it out functionality is not implemented yet for OAS3.

[jblazquez]

I can definitely use the try it out functionality for OAS3 with the current version in the ft/oas3 branch. Everything appears to work when using regular parameters, with the exception of request bodies (request bodies are sent, but they literally are always the example JSON based on the model).

[webron]

I'll rephrase - it's not supported. We need to make substantial changes to it and we've yet to start working on it. In fact, before the upcoming release of it, we'll disable the try-it-out button.

[shockey]

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 😄

[shockey]

Also see: #3338.

[shockey]

Closing; #3338 will track this feature being implemented.