feat: adds 'ancestor' matcher

[sverweij]

Description

• adds an ancestor matcher

Motivation and Context

It's probably possible to do this with regular expressions and group matching, but so far I haven't found a simple way to do that.

How Has This Been Tested?

• green ci
• additional automated integration tests
• additional automated unit tests
• self-run (added a no-ancestors rule to our own .dependency-cruiser.mjs)

Screenshots

You can now do things like this:

// in the `forbidden` section of a dependency-cruiser config:
{
  name: "no-ancestor",
  comment: "don't allow importing from folders above the current one",
  severity: "error",
  from: {},
  to: { "ancestor": true }
}

Which, when run as part of a validation, would yield errors on every dependency that goes folders up in stead of down:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Documentation only change
• Refactor (non-breaking change which fixes an issue without changing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• 📖

  • My change doesn't require a documentation update, or ...
  • it does and I have updated it

• ⚖️

  • The contribution will be subject to The MIT license, and I'm OK with that.
  • The contribution is my own original work.
  • I am ok with the stuff in CONTRIBUTING.md.

[codeclimate]

Code Climate has analyzed commit befba72 and detected 0 issues on this pull request.

View more on Code Climate.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud