fix(ref): Add missing context for resolve diffing

This commit is contained in:
Ed Page 2024-02-15 08:12:53 -06:00
parent 040a981523
commit d08e04f3a7
1 changed files with 1 additions and 1 deletions

View File

@ -830,7 +830,7 @@ Whether we do this and how much will be subject to factors like noisy output, pe
Some approaches we can take for doing this include:
We then do a depth-first diff of the trees, stopping and reporting on the first different node.
After resolving, we can do a depth-first diff of the trees, stopping and reporting on the first different node.
This would let us report on any command that changes the way the tree is resolved
(from explicit changes with `cargo update` to `cargo build` syncing `Cargo.toml` changes to `Cargo.lock`).
We'd likely want to limit the output to only the sub-tree that changed.