dennisdoomen / packageguard / 35877417864

82%

Build Type

push

github

Committed by web-flow

Commit Message

Find configuration files when a project lives outside the solution directory (#265)

* Find the solution-level configuration when a project lives outside the solution directory

Analyzing a solution whose projects aren't all nested under the solution
directory (for example a solution in "src/" that references sibling
"build/" or "tests/" projects) crashed with "Either a allowlist or a
denylist must be specified". Configuration discovery only walked upward
from each project's own directory looking for an ancestor that contained
the solution file, so any project outside that ancestor chain ended up
with no configuration at all and failed policy validation.

Configuration discovery now falls back to the directory that was
originally scanned when the upward search finds nothing, so the
solution-level configuration is still found for projects the solution
references from outside its own folder. An empty scan root, which is
the default when no path is given on the command line, resolves to the
current directory, matching how the rest of the tool already treats it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* Log which directories were searched for configuration files

Diagnosing why a project ended up with no allow/deny policy meant
guessing at which directories were checked for a packageguard.config.json
or .packageguard/config.json, since nothing was reported when a
directory was searched but came up empty.

Verbose mode now logs every directory that configuration discovery
looks in, along with any configuration file it finds there, making it
possible to see exactly where the search went without reading the
source.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Coverage Stats

2165 of 2904 branches covered (74.55%)

Branch coverage included in aggregate %.

9 of 11 new or added lines in 3 files covered. (81.82%)

4 existing lines in 2 files now uncovered.

6786 of 7991 relevant lines covered (84.92%)

1696.21 hits per line