Extension keeps complaining about no bazel file found.

Not all usages of Visual Studio Code has to be for working on projects which are using Bazel. Yet, when opening a directory or project which isn't using Bazel, the user keeps getting an error:


This error is excessive and contrary to the UX guide of VSCode extensions. If the extension doesn't find a Bazel file when opening a project, it should silently disable itself for this project, not annoy the user about it.

Start by opening a directory without a Bazel file in Visual Studio Code and reproduce the notification. Trace the extension's startup or project-detection behavior to find where the error is shown. Done means non-Bazel projects silently disable Bazel support without displaying the complaint.

Written by the indexing model from the issue text.