Extension cannot find bazel root without a WORKSPACE file

[leryss]

In pure bzlmod projects where there is no WORKSPACE file, the extension cannot find the root of the project and all paths become absolute as seen in the screenshot below. Is this intended?

[cameron-martin]

A reproducer for this would be appreciated.

[leryss]

remove the WORKSPACE file and restart vscode
go to any target and the gray path added by the extension will become absolute

[cameron-martin]

Unfortunately I cannot reproduce this. If you could give me a repository to reproduce this, plus tell me the version of the extension you are using, that would be helpful.