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

VSCode extension: default oxc_language_server.configPath seems wrong #5802

Open
greeeg opened this issue Sep 16, 2024 · 0 comments
Open

VSCode extension: default oxc_language_server.configPath seems wrong #5802

greeeg opened this issue Sep 16, 2024 · 0 comments
Labels
C-bug Category - Bug

Comments

@greeeg
Copy link

greeeg commented Sep 16, 2024

Hi 👋

While trying to move part of my linting config from eslint to oxlint, I did not understand why removing the no-console rule from .eslintrc & adding it to .oxlintrc.json did not trigger an error in my VSCode editor while it was triggering it properly running the oxlint CLI.

After a short investigating, I discovered that the default config path used by the OXC VSCode language server was .eslintrc.

It means that the oxlint language server was using my legacy eslint config instead of the new appropriate one. Should we change the default config path to be the filename documented here or at least explain that the configuration file used can be changed using VSCode settings.json file? Many thanks!

@greeeg greeeg added the C-bug Category - Bug label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category - Bug
Projects
None yet
Development

No branches or pull requests

1 participant