-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Document tryItOutEnabled parameter #3678
Comments
I don't follow, the |
Per https://github.com/swagger-api/swagger-ui/blob/master/docs/version-detection.md, try it out is not enabled by default. I am using swagger-ui v3.2.1 and binding to OpenApi spec v3.0, and the try it out button is not displaying. Are there v3.0 spec requirements/properties that must be set in order for try it out button to render? UPDATE: after deploying our app that is hosting swagger-ui to the remote host, the server drop-down and try it out buttons are now displaying. Running locally, it is hidden |
@jjohs there are two separate things. The 'try it out' not being enabled by default - I need to reword that - what I meant there was that the try it out is a two-step process. Clicking the button opens up the form, and only then you can execute the call. In 3.1, when we introduced OAS3 support, the try it out functionality was just not available to OAS3 at all - it wasn't just 'disabled', it didn't even show the button. In 3.2 that has changed. If you're using 3.2 and you're seeing weird behavior - please file a separate ticket with details to help us investigate. |
I'm using the latest version and the "try-it-out" button is enabled by default. How do I disable it? |
I see a number of references to a |
@curtisdf, good thought, but |
Closing as there's nothing to document at the moment. |
Thanks for the clarification, @shockey. I understand. |
Hi.
We would like to enable
try-it-button
, but there's no info in README.I have to figure that out, there is an option
tryItOutEnabled
you should place to your config.Should I prepare PR?
The text was updated successfully, but these errors were encountered: