On Fri, Oct 15, 2021 at 09:20:34PM +0000, Lessley Dennington via GitGitGadget wrote:
> From: Lessley Dennington <lessleydennington@xxxxxxxxx>
>
> Enable the sparse index within the 'git diff' command. Its implementation
> already safely integrates with the sparse index because it shares code with
> the 'git status' and 'git checkout' commands that were already integrated.
Good, it looks like most of the heavy-lifting to make `git diff` work
with the sparse index was already done elsewhere.
It may be helpful here to include either one of two things to help
readers and reviewers understand what's going on:
- A summary of what `git status` and/or `git checkout` does to work
with the sparse index.
- Or the patches which make those commands work with the sparse index
so that readers can refer back to them.
Having either of those would help readers who are unfamiliar with
builtin/diff.c convince themselves more easily that setting
'command_requires_full_index = 0' is all that's needed here.
> The most interesting thing to do is to add tests that verify that 'git diff'
> behaves correctly when the sparse index is enabled. These cases are:
>
> 1. The index is not expanded for 'diff' and 'diff --staged'
> 2. 'diff' and 'diff --staged' behave the same in full checkout, sparse
> checkout, and sparse index repositories in the following partially-staged
> scenarios (i.e. the index, HEAD, and working directory differ at a given
> path):
> 1. Path is within sparse-checkout cone
> 2. Path is outside sparse-checkout cone
> 3. A merge conflict exists for paths outside sparse-checkout cone
Nice, these are all of the test cases that I would expect to demonstrate
interesting behavior.
> diff --git a/t/t1092-sparse-checkout-compatibility.sh b/t/t1092-sparse-checkout-compatibility.sh
> index f19c1b3e2eb..e5d15be9d45 100755
> --- a/t/t1092-sparse-checkout-compatibility.sh
> +++ b/t/t1092-sparse-checkout-compatibility.sh
> @@ -386,6 +386,46 @@ test_expect_success 'diff --staged' '
> test_all_match git diff --staged
> '
>
> +test_expect_success 'diff partially-staged' '
> + init_repos &&
> +
> + write_script edit-contents <<-\EOF &&
> + echo text >>$1
> + EOF
> +
> + # Add file within cone
> + test_sparse_match git sparse-checkout set deep &&
> + run_on_all ../edit-contents deep/testfile &&
> + test_all_match git add deep/testfile &&
> + run_on_all ../edit-contents deep/testfile &&
> +
> + test_all_match git diff &&
> + test_all_match git diff --staged &&
> +
> + # Add file outside cone
> + test_all_match git reset --hard &&
> + run_on_all mkdir newdirectory &&
> + run_on_all ../edit-contents newdirectory/testfile &&
> + test_sparse_match git sparse-checkout set newdirectory &&
> + test_all_match git add newdirectory/testfile &&
> + run_on_all ../edit-contents newdirectory/testfile &&
> + test_sparse_match git sparse-checkout set &&
> +
> + test_all_match git diff &&
> + test_all_match git diff --staged &&
> +
> + # Merge conflict outside cone
> + # The sparse checkout will report a warning that is not in the
> + # full checkout, so we use `run_on_all` instead of
> + # `test_all_match`
> + run_on_all git reset --hard &&
> + test_all_match git checkout merge-left &&
> + test_all_match test_must_fail git merge merge-right &&
> +
> + test_all_match git diff &&
> + test_all_match git diff --staged
> +'
> +
> # NEEDSWORK: sparse-checkout behaves differently from full-checkout when
> # running this test with 'df-conflict-2' after 'df-conflict-1'.
> test_expect_success 'diff with renames and conflicts' '
> @@ -800,6 +840,11 @@ test_expect_success 'sparse-index is not expanded' '
> # Wildcard identifies only full sparse directories, no index expansion
> ensure_not_expanded reset deepest -- folder\* &&
>
> + echo a test change >>sparse-index/README.md &&
> + ensure_not_expanded diff &&
Thinking aloud here as somebody who is unfamiliar with the sparse-index
tests. ensure_not_expanded relies on the existence of the "sparse-index"
repository, and its top-level README.md is outside of the
sparse-checkout cone.
That makes sense, and when I create a repository with a file outside of
the sparse-checkout cone and then run `git diff`, I see no changes as
expected.
But isn't the top-level directory always part of the cone? If so, I
think that what this (and the below test) is demonstrating is that we
can show changes inside of the cone without expanding the sparse-index.
Having that test makes absolute sense to me. But I think it might also
make sense to have a test that creates some directory structure outside
of the cone, modifies it, and then ensures that both (a) those changes
aren't visible to `git diff` when the sparse-checkout is active and (b)
that running `git diff` doesn't cause the sparse-index to be expanded.
Thanks,
Taylor
