search

biomejs / biome-vscode

Biome extension for Visual Studio Code
https://marketplace.visualstudio.com/items?itemName=biomejs.biome
Apache License 2.0
162 stars 18 forks source link

🐛 Biome extension does not follow the local configuration #245

Open Embers-of-the-Fire opened 1 month ago

Embers-of-the-Fire commented 1 month ago

VS Code version

1.90.1

Extension version

2.3.0

Biome version

1.8.1

Operating system

Description

Files that have been opened before modifying biome.json will be affected by the modified configuration, but the linter will be restored after closing and reopening.

Running biome check from the local command line, biome works fine.

Screenshots:

Before saving config file: before saving config file

Immediately after saving config file: immediately after saving config file

Reopen the target file: reopen the target file

Steps to reproduce

  1. Init the config file with biome init.
  2. Modify the config file.
  3. Open a new file tab in vscode.

Expected behavior

In theory, biome should be able to read local configuration files.

Does this issue occur when using the CLI directly?

No

Logs

No output is found.
ematipico commented 1 month ago

I believe I know what's going on

MarArMar commented 2 weeks ago

I am experiencing this : closing & reopening VSCode works to solve the problem but it is not practical at all