Skip to content
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.

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

[Feature Request] A more friendly way to mark the "no-trailing-space" in the editor #731

Closed
semenov-k opened this issue Aug 16, 2019 · 4 comments
Labels
feature-request Request for new features or functionality upstream

Comments

@semenov-k
Copy link

I have a bit confusing thing.
space
When I see an error like in the picture above, I cannot say what exactly the type of error I have. It seems like Unexpected token error. I should go to the "PROBLEMS" tab and find that's eslint(no-trailing-space) error. But if to mark the "trailing space", I will see that I should remove it. Like in the picture below.
space_fixed

@semenov-k semenov-k changed the title A more friendly way to mark the "no-trailing-space" in the editor. [Feature Request] A more friendly way to mark the "no-trailing-space" in the editor Aug 16, 2019
@dbaeumer
Copy link
Member

Currently the ESLint extension doesn't modify the error ranges provided by eslint itself. However I see that for this particular problem moving it might be helpful although I could argue that eslint itself could profit from this as well. Have you talked to the eslint folks about this.

@dbaeumer dbaeumer added info-needed Issue requires more information from poster feature-request Request for new features or functionality labels Aug 19, 2019
@semenov-k
Copy link
Author

@dbaeumer, not yet. I will write to them.

@dbaeumer dbaeumer removed the info-needed Issue requires more information from poster label Oct 23, 2019
@dbaeumer dbaeumer added this to the Backlog milestone Oct 23, 2019
@golopot
Copy link

golopot commented Apr 7, 2020

I believe this is fixed by eslint/eslint#12477.

@dbaeumer
Copy link
Member

dbaeumer commented Apr 8, 2020

@golopot thanks. Will close the issue as upstream then.

@dbaeumer dbaeumer closed this as completed Apr 8, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators May 23, 2020
@dbaeumer dbaeumer removed this from the Backlog milestone Dec 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality upstream
Projects
None yet
Development

No branches or pull requests

3 participants