TSlint lists Problems in VSCode for Git Diff files
up vote
0
down vote
favorite
My Problem
When I compare two versions of a file with VS Code and the built-in Git features TSLint does not ignore the revisions but marks the errors. Since the diff files are located in AppDataLocalTemp on Windows the path checking fails and other things as well.
However, most annoying is not the red line in the file view but that they are listed in the Problem Panel and I get like 20+ problems just because opening one file revision and they won't go away until I reopen VS Code, so they add up during time.
That makes the panel useless for me, since I see lots of pseudo-problems, I won't notice an actual problem.
What I tried
I tried in my settings.json
"tslint.exclude": ["**/AppData/**"]
but that didn't work out.
Any suggestions would be much appreciated.
visual-studio-code git-diff tslint
asked Nov 20 at 12:27
Leun4m
1014
add a comment |
up vote
0
down vote
favorite
My Problem
When I compare two versions of a file with VS Code and the built-in Git features TSLint does not ignore the revisions but marks the errors. Since the diff files are located in AppDataLocalTemp on Windows the path checking fails and other things as well.
However, most annoying is not the red line in the file view but that they are listed in the Problem Panel and I get like 20+ problems just because opening one file revision and they won't go away until I reopen VS Code, so they add up during time.
That makes the panel useless for me, since I see lots of pseudo-problems, I won't notice an actual problem.
What I tried
I tried in my settings.json
"tslint.exclude": ["**/AppData/**"]
but that didn't work out.
Any suggestions would be much appreciated.
visual-studio-code git-diff tslint
asked Nov 20 at 12:27
Leun4m
1014
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My Problem
When I compare two versions of a file with VS Code and the built-in Git features TSLint does not ignore the revisions but marks the errors. Since the diff files are located in AppDataLocalTemp on Windows the path checking fails and other things as well.
However, most annoying is not the red line in the file view but that they are listed in the Problem Panel and I get like 20+ problems just because opening one file revision and they won't go away until I reopen VS Code, so they add up during time.
That makes the panel useless for me, since I see lots of pseudo-problems, I won't notice an actual problem.
What I tried
I tried in my settings.json
"tslint.exclude": ["**/AppData/**"]
but that didn't work out.
Any suggestions would be much appreciated.
visual-studio-code git-diff tslint
asked Nov 20 at 12:27
Leun4m
1014
My Problem
When I compare two versions of a file with VS Code and the built-in Git features TSLint does not ignore the revisions but marks the errors. Since the diff files are located in AppDataLocalTemp on Windows the path checking fails and other things as well.
However, most annoying is not the red line in the file view but that they are listed in the Problem Panel and I get like 20+ problems just because opening one file revision and they won't go away until I reopen VS Code, so they add up during time.
That makes the panel useless for me, since I see lots of pseudo-problems, I won't notice an actual problem.
What I tried
I tried in my settings.json
"tslint.exclude": ["**/AppData/**"]
but that didn't work out.
Any suggestions would be much appreciated.
visual-studio-code git-diff tslint
visual-studio-code git-diff tslint
asked Nov 20 at 12:27
Leun4m
1014
asked Nov 20 at 12:27
Leun4m
1014
asked Nov 20 at 12:27
Leun4m
1014
asked Nov 20 at 12:27
Leun4m
1014
asked Nov 20 at 12:27
Leun4m
1014
1014
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
answered Nov 28 at 14:24
Leun4m
1014
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53392989%2ftslint-lists-problems-in-vscode-for-git-diff-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
answered Nov 28 at 14:24
Leun4m
1014
add a comment |
up vote
0
down vote
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
answered Nov 28 at 14:24
Leun4m
1014
add a comment |
up vote
0
down vote
up vote
0
down vote
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
answered Nov 28 at 14:24
Leun4m
1014
Well, it appears that this is an issue with the GitLens extension which will be fixed with the upcoming version:
this issue has been fixed in the GitLens 9 release which will be coming very soon.
~ eamodio
(Source: https://github.com/eamodio/vscode-gitlens/issues/430#issuecomment-440731347)
answered Nov 28 at 14:24
Leun4m
1014
answered Nov 28 at 14:24
Leun4m
1014
answered Nov 28 at 14:24
Leun4m
1014
answered Nov 28 at 14:24
Leun4m
1014
1014
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53392989%2ftslint-lists-problems-in-vscode-for-git-diff-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
