Ignore or define folders

[dradickLRE]

This is may just be a question, not an issue. (Couldn't find a twitter handle)

Is there a way to configure certain folders to ignore .css files in?

Several of my projects have a template folder within the root that is just for reference. Any actual files being used are moved into a proper public folder. I suppose defining one or multiple folders could be an option as well. This may help speed up the drag on VSCode the extension has when building the cache.

[eko3alpha]

I'm having this issue as well. I've not found a way to prevent it from scanning my node_modules and vendor directories.

[manuelricci]

Same here... implement a method to ignore certain folder would be really appreciated.

[sabinrimni]

I would like this feature for another reason. My "Problems" view is cluttered with css issues from the "node_modules" folder and I would like to exclude it from the linting.

[nealoke]

I've just discoverd it also covers all my node_modules which is totally unnecessary for my project. Any way I could help @zignd ?

[zignd]

@nealoke Yup and would be greatly appreciated. If you're interested you can create a pull request implementing a contributes.configuration that would allow the users to specify folders to be ignored. And then you use this configuration during the search for supported files to ignore the specified paths.

[nealoke]

@zignd I'll look if I have time, any pointers on first contributing to a vscode extension? :)

[zignd]

@nealoke Let me see:

• Clone the repo
• Install Yarn
• yarn install for the dependencies
• code . in the repository directory
• Make your changes
• F5 to run the extension in Debug mode
• New window opens up with an isolated VS Code instance running and the extension will be already installed in it
• You can set break points in the VS Code containing the extension code (not the one running the extension installed)

In case you have any other doubts feel free to contact me, there's some contact info in my profile bio. :)

[zignd]

@nealoke I forgot to mention, documentation related to how VS Code extensions work can be found here: Extensibility Reference. And here is the documentation for the classes, methods, functions and everything code-related: vscode namespace API. Very useful resources.

[PixelT]

+1 for this "issue"
Now it's cache all CSS in node_modules which isn't a good idea :)

[zignd]

The recently released version adds a feature that is supposed to solve this issue.