You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the output of violations is grouped by class (fqcn), and all violations are listed under that. If violations were additionally grouped per rule, this could add to the clarity of the output AND reduce the line-length by splitting into more lines.
The output would look something like this:
App\Domain\Model has 2 violations:
violated rule: should not depend on classes outside namespace App\Domain because we want protect our domain
- App\Domain\Model depends on App\Services\UserService (on line 14)
- App\Domain\Model depends on App\Services\OtherService (on line 26)
violated rule: should implement EntityInterface
This idea came up in discussion in this PR: #281 (comment)
I'd be able to pick this up and create a pull request when I have some spare time if this is a wanted feature
The text was updated successfully, but these errors were encountered:
Feature Request
Summary
Currently the output of violations is grouped by class (fqcn), and all violations are listed under that. If violations were additionally grouped per rule, this could add to the clarity of the output AND reduce the line-length by splitting into more lines.
The output would look something like this:
This idea came up in discussion in this PR: #281 (comment)
I'd be able to pick this up and create a pull request when I have some spare time if this is a wanted feature
The text was updated successfully, but these errors were encountered: