Skip to content

Wrong caching causes the eslint vscode extension to error when creating files #981

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.

Sign up for GitHub

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

Jump to bottom
Closed
HosseinAgha opened this issue Sep 17, 2019 · 1 comment
Closed

Wrong caching causes the eslint vscode extension to error when creating files #981

HosseinAgha opened this issue Sep 17, 2019 · 1 comment
Labels
package: parser Issues related to @typescript-eslint/parser triage Waiting for team members to take a look

Comments

@HosseinAgha
Copy link

What did you expect to happen?

eslint should properly lint typescript new files in vscode.

What actually happened?

Please refer to this issue microsoft/vscode-eslint#738 and this comment microsoft/vscode-eslint#738 (comment)
It seems there is a problem with how you cache files in eslint --watch that causes eslint extension for vscode to show errors.

Versions

package version
@typescript-eslint/parser 2.3.0
TypeScript 3.5.3
ESLint 6.3.0
node 12
@HosseinAgha HosseinAgha added package: parser Issues related to @typescript-eslint/parser triage Waiting for team members to take a look labels Sep 17, 2019
@HosseinAgha
Copy link
Author

Sorry I think it is the dup for #864

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
package: parser Issues related to @typescript-eslint/parser triage Waiting for team members to take a look
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HosseinAgha