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

Set VSCode Exclude Files based on project Tags #1970

Open
andrebraghini opened this issue Dec 21, 2023 · 0 comments
Open

Set VSCode Exclude Files based on project Tags #1970

andrebraghini opened this issue Dec 21, 2023 · 0 comments
Labels
type: feature New feature or request

Comments

@andrebraghini
Copy link

Description

I would like to suggest the addition of a feature in the NX extension for Visual Studio Code (VSCode). Specifically, I propose the inclusion of an option that allows users to easily hide projects based on project tags. Currently, the VSCode extension supports the use of File Excludes, but it is a static configuration. I envision a user-friendly option within the extension that enables dynamic management of this configuration, making it convenient to focus on specific projects within the repository.

Motivation

The motivation behind this feature is to enhance the user experience when working with mono repositories. By providing a simple way to hide projects based on user-defined tags, developers can streamline their workflow and concentrate on relevant projects, thereby increasing productivity and reducing visual clutter.

Suggested Implementation

I propose the addition of a new option in the NX extension's user interface, accessible through a shortcut or a dedicated menu. This option should allow users to use already defined tags on projects and dynamically update the File Excludes configuration accordingly. The user interface can include an input field for tags and a checkbox or toggle to enable/disable the filtering of projects based on these tags. This way, users can easily customize their view within VSCode, tailoring it to their specific development needs.

Alternate Implementations

An alternative approach could involve integrating this functionality directly into the VSCode settings.json file, allowing users to manage project tags and visibility through a configuration file. However, a dedicated user interface within the NX extension would likely provide a more accessible and user-friendly experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant