Open mwilliammyers opened 5 years ago
Thanks, I'm looking forward to this! :)
Thanks for working on this @mwilliammyers! What does it do if you set the --depth=1
, and your dependency tree looks like this?
A
|- B
|- C
However, A
, B
, and C
are all in your workspace.
I think the ideal solution to #60 would let you show only dependencies referenced directly in your Cargo.toml
files (ie. the things you've specified, local or remote).
Assuming A
is your "main" (or lib) crate then it would do:
A
|- B
@sfackler if I fix the conflicts with master, is this a feature that you would consider adding?
Adds the
-D <DEPTH>
/--depth <DEPTH>
option.Closes #60
Example:
Things to consider:
*
printed later on. This might lead to confusing behavior when used with the--duplicate
option though?--package
as the "root" package, i.e. instead of erroring:because
syn
is a transitive dependency with a depth>1
, it prints out the dependencies ofsyn
that have a depth<=1
fromsyn
(not the real package root):Is this the desired behavior?
*
when truncating a dependency whose children are not being printed because they are above the--depth
limit and is also a duplicate?