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 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
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.
Possible Solution
I thought the bug was happened after the fix for path item $ref rendering (via #4381) in 3.13.2
The text was updated successfully, but these errors were encountered:
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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
and in book.json:
Expected Behavior
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.

Possible Solution
I thought the bug was happened after the fix for path item $ref rendering (via #4381) in 3.13.2
The text was updated successfully, but these errors were encountered: