Skip to content
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

Support to contribute a custom view so that it is only visible in the Views menu of view's container #101283

Closed
egamma opened this issue Jun 29, 2020 · 2 comments · Fixed by #102002
Assignees
Labels
Milestone

Comments

@egamma
Copy link
Member

egamma commented Jun 29, 2020

Currently it is not possible to contribute a custom view so that it is visible in the 'Views' menu only but not also in the View Container. This will help to improve the 1st run experience and to reduce the clutter of the Explorer view, e.g., the NPM Script Explorer would no longer be visible by default (when there is a package.json)

@alexr00
Copy link
Member

alexr00 commented Jul 9, 2020

Current contribution point:

    "views": {
      "explorer": [
        {
          "id": "npm",
          "name": "%view.name%",
          "when": "npm:showScriptExplorer || config.npm.enableScriptExplorer",
          "icon": "images/code.svg"
        }
      ]
    }

Proposal is to add visibility which can be set to visible(default), hidden, or collapsed. Example:

    "views": {
      "explorer": [
        {
          "id": "npm",
          "name": "%view.name%",
          "when": "npm:showScriptExplorer || config.npm.enableScriptExplorer",
          "icon": "images/code.svg",
          "visibility": "hidden"
        }
      ]
    }

@alexr00
Copy link
Member

alexr00 commented Jul 29, 2020

This has been finalized.

@alexr00 alexr00 closed this as completed Jul 29, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Sep 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants