Skip to content

Proper handling of other-side --ignore in report() #35

@defuse

Description

@defuse

Scenario: The user passes --ignore a/foo/bar, which exists, but during the comparison, a/foo errors out. In this case, it will report b/foo as missing. Currently, this means it will also report b/foo/bar as missing even though the semantics of --ignore in compare() mean "ignore this side, as well as the equivalent path on the other side."

We probably want to keep the same semantics as in compare(), since the user might be trying to ignore a really big directory that exists on both sides, and a transient error on one side shouldn't cause that whole big directory on the other side to be reported.

See #36 for defining the complete semantics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions