Skip to content

tests: add contents_first with min & max depth - #164

Open
danielparks wants to merge 1 commit into
BurntSushi:masterfrom
danielparks:test_contents_first_min_max
Open

tests: add contents_first with min & max depth#164
danielparks wants to merge 1 commit into
BurntSushi:masterfrom
danielparks:test_contents_first_min_max

Conversation

@danielparks

Copy link
Copy Markdown

This just adds contents_first(true) versions of the existing tests for min and max depth. Given that handling contents first can be a bit confusing, it seemed wise to test it more thoroughly.

For symmetry, this switches the existing min and max depth tests to use path() instead of sorted_paths(). Because all of the test directories only have one entry, there should never be an issue with entries being returned in a different, but still correct, order.


This isn’t strictly necessary, but when I was working on #163 I was concerned that min and max depth might break with contents_first. No worries if you’d prefer not to add these, or if you’d prefer to keep sorted_paths().

This just adds `contents_first(true)` versions of the existing tests for
min and max depth. Given that handling contents first can be a bit
confusing, it seemed wise to test it more thoroughly.

For symmetry, this switches the existing min and max depth tests to use
`path()` instead of `sorted_paths()`. Because all of the test
directories only have one entry, there should never be an issue with
entries being returned in a different, but still correct, order.
@danielparks
danielparks force-pushed the test_contents_first_min_max branch from dfa44f0 to 3ba1cc0 Compare December 30, 2025 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant