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

Configuration to use a formatter #1928

Open
bartocc opened this issue Sep 6, 2024 · 2 comments
Open

Configuration to use a formatter #1928

bartocc opened this issue Sep 6, 2024 · 2 comments
Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities
Milestone

Comments

@bartocc
Copy link

bartocc commented Sep 6, 2024

In our codebase, we use [email protected] and https://github.com/lint-todo/eslint-formatter-todo to create a .lint-todo file that will keep track of all the places where we have eslint errors. The codebase is large, and this is very handy to plan the fixes and never loose track of them.

In the CLI, eslint . --format @lint-todo/eslint-formatter-todo is the command we use, and all the TODOs are silenced until they hit their error date.

But in VSCode, we still see the errors because the formatter is not used by vscode-eslint.

I am looking for a way to do so, and did not find any extension option for this.

Is that possible?

cc: @fannyvanrell

@dbaeumer
Copy link
Member

dbaeumer commented Sep 9, 2024

This is currently not possible since the ESLint extension doesn't print any detected problems to the console.

What I can think of is using a task and run ESLint as a normal OS process. Task are very flexible and I am pretty sure you can configure one that does the work. The only downside is that for task there aren't any automatic triggers. So you need to run / trigger them from time to time yourself.

Let me know if that helps.

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label Sep 9, 2024
@bartocc
Copy link
Author

bartocc commented Sep 9, 2024

Thk @dbaeumer for the ideas about tasks. I'll see if this can fit our dev process…

@dbaeumer dbaeumer added feature-request Request for new features or functionality and removed info-needed Issue requires more information from poster labels Sep 10, 2024
@dbaeumer dbaeumer added this to the Backlog milestone Sep 10, 2024
@dbaeumer dbaeumer added the help wanted Issues identified as good community contribution opportunities label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality help wanted Issues identified as good community contribution opportunities
Projects
None yet
Development

No branches or pull requests

2 participants