added filtering to tree command to show only paths that lead to targe… #305
Conversation
There was a problem hiding this comment.
Without reviewing the actual code.
I think what you want here is actually --invert.
Eg rv tree --invert=data.table that would put data.table at the top and then a tree of everything depending on it. We talked about adding --invert before, that would be a good time
| ``` | ||
|
|
||
| ## JSON Output Support | ||
| All tree structures implement `Serialize` for JSON output, enabling programmatic consumption of dependency tree data. No newline at end of file |
There was a problem hiding this comment.
Are we going to commit all the Claude stuff? Most of this seem to be thing the llm should pick up anyway from looking at the structs and might be out of date
There was a problem hiding this comment.
from the claude code best practices the ai-references should be used to help guide it and improve its understanding of where to find stuff so it doesn't search so much. but to your comment below, they need to be auditted very carefully
| **Key Fields:** | ||
| - `name`: Package name | ||
| - `version`: Package version (if resolved) | ||
| - `source`: Where the package comes from (lockfile, repository, git, etc.) |
There was a problem hiding this comment.
See that's wrong there, a package never comes from the lockfile
…t package
I had an issue with a broken binary of data.table in my package, but I wasn't sure where it was coming from.
rv treecan help, but I wanted a--package data.tableflag to filter the tree to show me how it was being introduced. This PR adds that functionality