Thanks to Maria for actually testing the new --exclude option from a user's POV, and notifying me of various griveous issues found. Here we try to tackle the ones that were found and raise in the later stages of #388:
Running fawltydeps with --exclude and passing relative paths instead of absolute (our test suite relies too heavily on absolute paths)
Passing "anchored" exclude patterns to --exclude was initially unsupported. Fix that.
Give the user a warning when the --exclude option directly overlaps with a given path (in which case the given path will always win).
Fix issues where the precedence between --exclude patterns and given paths were not followed in practice.
Thanks to Maria for actually testing the new
--excludeoption from a user's POV, and notifying me of various griveous issues found. Here we try to tackle the ones that were found and raise in the later stages of #388:fawltydepswith--excludeand passing relative paths instead of absolute (our test suite relies too heavily on absolute paths)--excludewas initially unsupported. Fix that.--excludeoption directly overlaps with a given path (in which case the given path will always win).--excludepatterns and given paths were not followed in practice.