You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So whenever I checkout the revision of a file (comparing commits) from GitLens File History sidebar (doesn't matter) the files in the diff view get linted by editor linters (ts, vscode-tslint, vscode-eslint) and all linting errors are shown in Problems panel and stay there after closing the diff view.
That seems like really an unexpected behavior because temp files are created in /var/folders/ and are not related to the project folder so linters should not lint these files at all. Morever, linted output stays in the Problems panel even when the files are closed and I couldn't find any other way to get rid of them other then Reload Window from command panel.
I was able to disable tslint linting with
"tslint.exclude": [
"**/var/folders/**/*.*",
]
but not vscode ts linter.
So is there any way to disable revision preview files from being linted or is this a bug?
@eamodio Is there a way to manually remove these files from the Problems View at least? When files are closed they are not listed in Opened Editors and seems there's no other way to ignore the Problems output.
So whenever I checkout the revision of a file (comparing commits) from GitLens File History sidebar (doesn't matter) the files in the diff view get linted by editor linters (ts, vscode-tslint, vscode-eslint) and all linting errors are shown in Problems panel and stay there after closing the diff view.
That seems like really an unexpected behavior because temp files are created in
/var/folders/
and are not related to the project folder so linters should not lint these files at all. Morever, linted output stays in the Problems panel even when the files are closed and I couldn't find any other way to get rid of them other then Reload Window from command panel.I was able to disable tslint linting with
but not vscode ts linter.
So is there any way to disable revision preview files from being linted or is this a bug?
GitLens output log
1.25.1
1dfc5e557209371715f655691b1235b6b26a06be
x64
macOS High Sierra 10.13.5 (17F77)
The text was updated successfully, but these errors were encountered: