-
Notifications
You must be signed in to change notification settings - Fork 40
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
Pin the OpenAPI button #78
Comments
Thanks for your feedback! I'll discuss it with the team, but for now I think it might be a reasonable approach to show OpenAPI button in the activity bar if user did open at least one OpenAPI file, and never hide it even if user switches away from the OpenAPI file. What do you think? |
Fixed |
So, we've fixed the issue using the new 'viewsWelcome' API, and this will make it so the OpenAPI button is shown at all times, from the start even if there is no OpenAPI files open. |
Sorry to bring back the issue My use case: I use vscode for many different projects and a majority of them doesn't require OpenAPI (example: working on a video game) Would it be possible to have a workspace setting to either globally show or hide the OpenApi button? Another approach would be to only show the button if the current file opened is |
Hi @lautriva this is something best handled by VS Code itself. I think you can enable/disable extensions per workspace (click on a gear icon in the extensions and there would be something like |
It would be nice and less jarring if the OpenAPI button would not disappear if I switch to another file. Maybe if the extension sees a
swagger.json
oropenapi.yml
, etc... file in the project it would not disappear.EDIT: It would also allow me to quickly get back to my api design to make any changes or reference any paths
The text was updated successfully, but these errors were encountered: