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
bazel.commandLine.commandArgs is only passed into bazel test and bazel build commands, not bazel query.
I have a scenario where I need to use --config or --package_path at the end of the command bazel query.
Can we add a configurable field to pass in args to bazel query? Currently, we have startupOptions which results to bazel [startupOptions] query. However, there isn't a way to have bazel query [additionalArgs].
The text was updated successfully, but these errors were encountered:
Would it be an option for you to define your query command line arguments in your .bazelrc file like so:
query --package_path=...
What would be cool though, I think, is if this extension offered some UI element to select configuration aliases per Bazel command from the ones available in your .bazelrc file.
Would it be an option for you to define your query command line arguments
Yes
What would be cool though, I think, is if this extension offered some UI element to select configuration aliases per Bazel command from the ones available in your .bazelrc file.
I'm not sure how feasible this is. Usually the configs are driven by the set of configs and their default values statically written in the package.json file. The .bazelrc is not static and dependent on specific repos.
However, it would be nice to be able to specify --config=<alias> somewhere in the configs window.
bazel.commandLine.commandArgs
is only passed intobazel test
andbazel build
commands, notbazel query
.I have a scenario where I need to use
--config
or--package_path
at the end of the commandbazel query
.Can we add a configurable field to pass in args to
bazel query
? Currently, we havestartupOptions
which results tobazel [startupOptions] query
. However, there isn't a way to havebazel query [additionalArgs]
.The text was updated successfully, but these errors were encountered: