parameter content type not working when defaultValue is used #593

akhil · 2014-09-19T20:39:56Z

I used http://demo0536639.mockable.io/api-docs at http://petstore.swagger.wordnik.com/
In the http://demo0536639.mockable.io/api-docs/assets there is "defaultValue": "{}", in 'parameters'
The textbox gets populated by {} as expected. But the dropdown is missing.

When I remove the defaultValue entry I see the dropdown

akhil mentioned this issue Sep 19, 2014

How can multiple response content types and parameter content type be set? #119

Closed

fehguy added this to the v2.1.0-M1 milestone Jan 28, 2015

fehguy added the type: bug label Jan 28, 2015

fehguy added a commit that referenced this issue Jan 30, 2015

fix for #593

e5b7923

fehguy closed this as completed Jan 30, 2015

mjumbewu pushed a commit to mjumbewu/swagger-ui that referenced this issue Mar 7, 2015

fix for swagger-api#593

e8115ef

Jonahss pushed a commit to eaze/swagger-ui that referenced this issue Aug 12, 2016

fix for swagger-api#593

2d32ab8

vincent-zurczak pushed a commit to roboconf/swagger-ui that referenced this issue Aug 18, 2016

fix for swagger-api#593

ccffa9a

enjame mentioned this issue Feb 4, 2021

[Snyk] Upgrade react-split-pane from 0.1.70 to 0.1.92 enjame/swagger-ui#1

Open

snyk-bot mentioned this issue Oct 6, 2021

[Snyk] Upgrade react-split-pane from 0.1.57 to 0.1.92 acima-credit/swagger-ui#6

Open

BrianVarner mentioned this issue Apr 29, 2023

[Snyk] Upgrade react-split-pane from 0.1.57 to 0.1.92 octanner/swagger-ui#1

Open

JuanSW18 pushed a commit to Digital-Paw/digital-paw-swagger-ui that referenced this issue Aug 23, 2024

fix for swagger-api#593

b23f275

Provide feedback