Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation of deps gives wrong description in example for limiting depth #5929

Closed
endobson opened this issue Aug 18, 2018 · 1 comment
Closed

Comments

@endobson
Copy link
Contributor

Description of the problem / feature request:

https://docs.bazel.build/versions/master/query.html#deps

The deps operator accepts an optional second argument, which is an integer literal specifying an upper bound on the depth of the search. So deps(foo:*, 1) evaluates to all the direct prerequisites of any target in the foo package, and deps(foo:*, 2) further includes the nodes directly reachable from the nodes in deps(foo:*, 1), and so on.

The example in the second sentence is wrong because deps(foo:*, 1) returns the direct prerequistes of any target in the foo package and all the targets in the foo package.

@aiuto aiuto added untriaged team-Bazel General Bazel product/strategy issues type: documentation (cleanup) labels Aug 19, 2018
@aiuto aiuto assigned aiuto and tualeron and unassigned aiuto Oct 3, 2018
@aiuto aiuto added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Oct 3, 2018
@dslomov dslomov added the team-Performance Issues for Performance teams label Jul 23, 2019
@dslomov dslomov added untriaged and removed P2 We'll consider working on this in future. (Assignee optional) team-Bazel General Bazel product/strategy issues labels Jul 23, 2019
@mehrdadn
Copy link

Yes, this is really confusing. Also, is there a way to get just the prerequisites themselves? That'd be a really useful feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants