Skip to content

Could not click on the item in the Parameter Content Type box in 3.13.2 -> 3.13.6 #4485

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
hnthu opened this issue Apr 27, 2018 · 3 comments
Closed

Comments

@hnthu
Copy link

hnthu commented Apr 27, 2018

Q A
Bug or feature request?
Which Swagger/OpenAPI version?
Which Swagger-UI version?
How did you install Swagger-UI?
Which browser & version?
Which operating system?

Demonstration API definition

When you reference to a json file or yaml file in your main json file or yaml file.
and the reference json file you define a consumes which contains more than one item.
Then you could not chose the other item in the parameter content type

put a $ref in your main.json

 "/v1/book": {
        "$ref": "book.json#/buy"
    },

and in book.json:

{
"post": {
"description": "Book",
"operationId": "buy",
"summary": "Buy a book",
"tags": [
"Book"
],
"consumes": [
"application/json",
"application/xml"
],
"parameters": [
{
"name": "requestBody",
"in": "body",
"description": "Buy a Book",
"required": true
}
]
}
}

Expected Behavior

image

User could click on the application/xml successfully.

Current Behavior

User couldn't click on the application/xml. After click on the application/xml the GUI still use application/json.
image

Possible Solution

I thought the bug was happened after the fix for path item $ref rendering (via #4381) in 3.13.2

@hnthu hnthu changed the title Could not click on the item in the Parameter Context Type box in 3.13.2 -> 3.13.6 Could not click on the item in the Parameter Content Type box in 3.13.2 -> 3.13.6 Apr 27, 2018
@shockey
Copy link
Contributor

shockey commented Apr 27, 2018

Bug confirmed!

I just finished a fix, which will be released today. Sorry for the trouble, and thanks for reporting!

@hnthu
Copy link
Author

hnthu commented Apr 28, 2018

A Massive thank you shockey for supporting this problem very quickly. Thank you very much.

@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