You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You get the expected Test //whatever:foo link, but you also get Build //whatever:foo_0__deps.
And if you have functions in a .bzl file that create multiple sub-rules, the list of links can quickly get very long, and end up wider than the available space, and the UI does not let you scroll right if your file content is not that wide.
(Incidentally, it would be nice to wrap these long lines of links, but that is a separate FR)
Ideally, it would just honor the existing Bazel › Command Line: Query Expression option for these links as well.
But it would be fine to have a similar option specifically for the CodeLens links if that is deemed to be nicer.
Thoughts?
The text was updated successfully, but these errors were encountered:
cameron-martin
changed the title
[Feature request] Add option to filer CodeLens links in BUILD files
[Feature request] Add option to filter CodeLens links in BUILD files
Jan 23, 2024
This would be really nice to have both for the CodeLens links but also for the side bar tree.
[...]
Alternatively just a setting to add filter by name.
For the side bar / the "Bazel Build Targets" tree, there is already the setting bazel.commandLine.queryExpression.
I guess you could write a Bazel query to filter out no-ide tagged targets?
TL;DR: It would be really nice to have a way to filter the displayed CodeLens links.
In BUILD files, there are often extra hidden rules defined by rules.
For example, if you use:
You get the expected
Test //whatever:foo
link, but you also getBuild //whatever:foo_0__deps
.And if you have functions in a
.bzl
file that create multiple sub-rules, the list of links can quickly get very long, and end up wider than the available space, and the UI does not let you scroll right if your file content is not that wide.(Incidentally, it would be nice to wrap these long lines of links, but that is a separate FR)
Ideally, it would just honor the existing
Bazel › Command Line: Query Expression
option for these links as well.But it would be fine to have a similar option specifically for the CodeLens links if that is deemed to be nicer.
Thoughts?
The text was updated successfully, but these errors were encountered: