🐛 biome.requireConfigFile Ignored When Opening Single File in VSCode

[LucasOe]

VS Code version

1.94.1

Extension version

2024.10.40751 (pre-release)

Biome version

1.9.3

Operating system

• Windows
• macOS
• Linux

Description

When biome.requireConfigFile is set to true, it is expected that Biome (linter/formatter) should only be activated if a valid configuration file is present. However, this behavior is inconsistent when opening a single file in VSCode. Biome appears to be enabled automatically, even if no configuration file is present, contrary to the setting. This issue does not occur when opening a directory, where Biome correctly respects the biome.requireConfigFile setting.

I only tested this issue on the pre-release version of the Biome Extension.

Steps to reproduce

1. Set "biome.requireConfigFile": true in your VSCode settings.
2. Open a single file in VSCode that does not have a Biome configuration file in the current directory or any parent directories.
3. Observe that Biome is enabled

Expected behavior

Biome should not be activated when opening a single file if no configuration file is present, respecting the "biome.requireConfigFile": true setting.

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs

No response

[nhedger]

In single-file mode, there won't be a biome.json in your workspace because there is no workspace by definition. Would you expect the extension to check for a configuration file in the file's parent folder?

[LucasOe]

Would you expect the extension to check for a configuration file in the file's parent folder?

Yes, I would expect Biome to behave the same whether a file is open in a workspace or in single file mode. I think most users who enable biome.requireConfigFile only want to see Biome's lints in a project that uses it, so having the file be linted if opened in single-file mode would probably be confusing.

[ematipico]

@nhedger i think we can move this issue in the main repo.

Biome LSP already accepts this configuration from the client, so Biome LSP should behave consistently, as long as the client sends this settings when reading the client configuration