Ignore folders/files in Problems view

[bravecobra]

The Problems View now lists all problems, even in 3rd party code like in node_modules, which is cluttering the actual problems of the opened project. You should be able to ignore certain folders/files while diagnosing/listing problems. This should be possible on a project basis, not as a VSCode setting. (thus in the .vscode/settings.json)

• VSCode Version: 1.10.2
• OS Version: Any

[dbaeumer]

@bravecobra what is the source of the problem. Usually you can configure this with the tool that generates these problems. Is it ESLint, JS, ...

[bravecobra]

I think that's the problem. I have no idea which tool is generating the errors or where to configure them. My workspace is filled with projects in JavaScript, TypeScript, C#, SCSS, HTML, etc.. One of my sub-folders contains an angular 2 project, another one contains an ASP.NET website, some of them are javascript or plain html5/CSS. All of them using 3rd party dependecies through nuget, npm, bower,etc
There is no indication which tool is generating these problems and/or what configuration it is using.

• I see linting on ESLint, TSLint, markdownlint (3 plugins I installed), which report that they could not be enabled since there is no config file in the root of the workspace (sure, it's in one of the subdirectories containing the project), but I do see warnings in typescript (which is not my code, but from a 3rd party test project)
• Omnisharp is spitting out errors (like I should add mscorlib while being on Linux and Windows simultaneously ) and my projects compiles perfectly using the dotnet cli. Errors coming from the selenium-webdriver's test project which got in through npm as I'm using e2e on Angular. I'm sure this is an Omnisharp problem, not a VSCode one.
• I see errors popping up on the minified css from bootstrap that got in through npm.
• SCSS linting is happening as well (of which the settings are in vscode) and gives errors in files inside node_modules
• Some problems also disappear when closing the file, others stay.

In other words, currently, the Problems view is no real added value to me as its behaviour "appears" random to me (I'm sure it is not). Without any indication of which tool/plugin/setting is generating the problem and where/how it can be configured, there is no way of ignoring/fixing 3rd party code. I'd be happy to configure each individual tool to ignore folders or files (if the tool provides that), but first I'd need to know which tool it is. Secondly, what if the tool itself doesn't provide such a feature and I choose to ignore the problem/warning (it might not be my own code), how would I make it disappear from the problems view? So the original question boils down to :

1. Indicate which tool/plugin/vscode-setting is giving the error and where it can be configured
2. If the tool doesn't provide a way for ignoring the error/warning, at least a way to ignore it, so it won't clutter your view on the actual problem of your own project code.

[dbaeumer]

Echo problem should start with a [*] indication pointing to a tool that generated the problem. So [ts] means TypeScript, [js] means JavaScript, [eslint] means ESLint, ....

Does that help identifying the tool generating your problems.

[bravecobra]

That would identify them (maybe), but still that would not allow for uncluttering the view. For instance, the build-in validation (https://code.visualstudio.com/docs/languages/css) does not allow me to specify folders to ignore (the vendor folders like node_modules) on a project basis. Just an [*] indication would indeed point you to a tool, which "might" enable you to un-clutter, so that still doesn't solve my second remark at the end of my previous reply. Adding a "problem view filter" setting in the .vscode folder on a project basis would do that. Indicating that x number of problems were hidden due to this setting, might even help to find incorrect items added to the setting. Basically, I want to right-click in the problems view on "ignore this problem"or "ignore problems in this folder" or something alike. The indicator would indeed allow you to configure the tool correctly so it doesn't spit out these problems, but as I said, the tool might not be able to do so.
PS: Why do problems go away from the problems view once you close the file? I expect to see all the problems of "my" code (not the vendor's), not just the ones of the opened files, sort of like the Error's List in Visual Studio. This might be a separate issue.

[mattiLeBlanc]

Any solution for this? I am having a similar issue where I got problems reported from stuff in my node_modules folder.

My TSCONFIG

{
  "compilerOptions": {
    "outDir": "./dist/",
    "sourceMap": true,
    "noImplicitAny": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "module": "commonjs",
    "target": "es5",
    "jsx": "react",
    "allowJs": true,
    "typeRoots": ["node_modules/@types/"],
    "types": [
      "node",
      "lodash",
      "angular"
    ]
  },
  "filesGlob": [
    "src/**/*.ts",
    "src/**/*.tsx",
    "!node_modules/**"
  ]
}

Not sure how to tell VS CODe to ignore these problems. Lot's of them are about README.md lines in node_modules

[proProbe]

Hello!
Im also running in to the problem of the built in css-linter shows error from the node_modules. Is it possible yet to set folders for it to ignore?

[cortopy]

I'm having same issue. I can't find how to configure in-built validators (css, html) to ignore folders like node_modules

[klis87]

I have related problem with html linting problems in node_modules directory when using IntelliSense for CSS class names plugin. When I click button to cache all CSS classes to have intellisense of available CSS classes, this plugin scans all directories to find CSS classes. The problem is, that those scans trigger linter rules for all scanned files. So I always end up with 99+ problems showed in PROBLEMS tab. I managed to get rid of CSS, SASS, LESS problems by disabling those totally, but I cannot see any option to disable HTML linter. It would be great to add it. Also, it would be even greater to add option to exclude custom directories from build in linters for CSS, SASS, LESS and HTML.

[atiris]

for me, it shows "problems" from .history folder which contains temporary versions of files (so it really is not a problem for my code). But on first places in Problems tab I still see that some old version of app.component.ts - app.component_20170515154207.ts was for few seconds saved in incorrect state.

Problem text (I assumed it comes from tslint, but this directory is ignored in settings):
[ts] Cannot find module './app-data'. (5, 33) ...

My settings already contains also this parts:

User settings

"files.exclude": {
  ...
  "**/.history": true
},
"files.watcherExclude": {
  ...
  "**/.history/**": true
},
"autoimport.filesToScan": "{src,e2e,node_modules}/**/*.{ts,tsx}",

Workspace settings

"tslint.exclude": ["**/dist/**", "**/.history/**", "**/node_modules/**"]

I do not know what else I could do anymore.