Reinstate biome.requireConfiguration

[lgarron]

This is a re-file of biomejs/biome#1943

Several of us are feeling the pain when Biome unceremoniously starts formatting projects it was never configured for. This isn't so just annoyance but also a straight-up liability for those of us who regularly work on codebases that do not have a Biome configuration.

Looking at #27 , it sounds like defaulting biome.requireConfiguration to false would address the main concerns that led to removal.

@wtchnm has also pointed out that this configuration is available in the zed extension: biomejs/biome#1943 (comment)

It would be really valuable to have this back in VS Code.

[nhedger]

Hey,

Thanks for opening this issue. The feedback was heard and the option has been re-introduced in the pre-release of the extension, where where we're currently focusing our efforts.

Are you able to try the pre-release ?

[lgarron]

Hey,

Thanks for opening this issue. The feedback was heard and the option has been re-introduced in the pre-release of the extension, where where we're currently focusing our efforts.

Are you able to try the pre-release ?

Aha! That explains why the codebase contained code for requireConfigFile.

I just upgraded to the pre-release, and I can confirm it addresses my concerns, thanks! 🤩