This functionality should be available if you configure a language server (see the README). Currently, that functionality is still experimental, also see #1 for a lot more context on the current state of language server support

Oh I see, thanks, I didn't know a language server had anything to do with this so I hadn't looked into that, definitely will now.

Hi @vogelsgesang , I went ahead and installed the language server (bazel-lsp) but have seen no difference in the behaviors I was explaining above.
Code navigation often still takes me to bazel's cache instead of the starlark BUILD sources, even when I add bazel's cache to the list of directories to ignore.

Is there some way of debugging this you would recommend? I am pretty new to starlark/bazel and really all I want is code navigation so I can navigate a huge source code base easily.

I am a bit confused.

Which language are you trying to use code navigation on? Starlark? C ? Python? some other language?

Starlark! basically I wanna be able to ctrl click on some dependencie of a bazel rule and be taken to that rule's definition

👍 ok, then I understood your initial post correctly.

I am not sure how the code navigation for Starlark should work. My best bet would have been that this should work with the Starlark-LSPs. @cameron-martin and @withered-magic might be able to provide more context on what works / doesn't work regarding Starlark code navigation, yet

It sounds like the ask here is for code navigation to resolve symlinks, like clangd does from memory. This may have unintended consequences on further code navigation when naively implemented, since it'll lose the context on what the bazel workspace is.

Do you mind opening an issue on bazel-lsp and starpls?