Feature request: Check if any import matches

Context

Our codebase is moving to a new arch and I want to add a warning if a module hasn’t been migrated yet. Essentially, I want to check if a type of dependency exists.

Let’s say I want to check if all the controller modules have been migrated, which I can simplify into a check to see if they extend the new base controller, for eg:

class 'AbcController' extends 'GenericController'

Expected Behavior

I want to check if AbcController contains an import for GenericController:

    {
      name: 'no-clean-arch-controller',
      severity: 'warn',
      "from": { "path": "^src\/api\/([^/]+)\/([a-zA-Z]+Controller.ts)"},
      "to": { 
        "pathNot": "src\/framework\/GenericController.ts" 
      },
    }

with the result:

no-clean-arch-controller: src/api/x/abcController.ts → src/framework/GenericController.ts

Current Behavior

It currently tells me about all the imports that aren’t GenericControllerImpl, and nothing

no-clean-arch-controller: src/api/x/abcController.ts → src/example/some-import.ts
no-clean-arch-controller: src/api/x/abcController.ts → src/example/another-import.ts

Possible Solution

A boolean to signify that there’s no dependency from A to B would be helpful.

Considered alternatives

I tried to make it work with allowed, but it became too complex and didn’t solve my issue anyway.

[hzaun]

I was using dependency-cruiser@9.9.0-beta-3, just updated to beta-4, it works as expected, thank you so much!

[sverweij]

Just a ping: I’ve done some polishing (published in beta-2, 3 and 4). Most notable change, only for the new required rules: the from attribute was renamed to module so in the future it’s possible to use the ‘from’ attribute for other useful things. E.g. to make sure each source file has an associated spec file in the unit tests folder that directly points to it:

// future feature
{
  required: [{
    name: "spec-per-source",
    comment: 'for each source file there should be at least a corresponding spec file in the test folder',
    module: {
      path: "^src/(.+)\\.js$"
    },
    from: {
      path: "^test/$1\\.spec\\.js$"
    }
  }]
}