We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/swagger-api/swagger-editor/pull/3385/files introduce some new items to the top bar. One of the is the "Try our new editor" button. We're self-hosting Swagger Editor for internal usage. The button will take people out of our self-hosted setup and they might not be aware of it.
An option to disable the "Try our new editor" button, in the best cased similar to other options: https://github.com/swagger-api/swagger-editor#running-the-image-from-dockerhub
/cc @antoineauger @dlouzan
The text was updated successfully, but these errors were encountered:
feat(topbar): allow to configure components present in Topbar
1674799
Refs #3556
feat(topbar): allow to configure components present in Topbar (#3623)
7f4aa5c
Changes released a docker image: swaggerapi/swagger-editor:v4.6.0
Using this version and above, there is no button present anymore.
Sorry, something went wrong.
char0n
No branches or pull requests
Is your feature request related to a problem?
https://github.com/swagger-api/swagger-editor/pull/3385/files introduce some new items to the top bar. One of the is the "Try our new editor" button. We're self-hosting Swagger Editor for internal usage. The button will take people out of our self-hosted setup and they might not be aware of it.
Describe the solution you'd like
An option to disable the "Try our new editor" button, in the best cased similar to other options: https://github.com/swagger-api/swagger-editor#running-the-image-from-dockerhub
/cc @antoineauger @dlouzan
The text was updated successfully, but these errors were encountered: