Yohan Blain

Currently the same Rule class is used for every rule type. As we move more logic to the domain it would be clearer to have a dedicated class by type.

Currently, most of the application logic is located in service-like classes (`CouplingDetector` and `RuleChecker`) while the domain is dumb. It would make sense to let the domain be responsible for...

We already have a Domain namespace. Could be interesting to also have Application (especially if we use a message bus at some point) and Infrastructure (Commands, Formatters, Parsers...)

Especially on domain objects (Rule, Node, etc.).

For example when [displaying violations of a discouraged rule](https://github.com/akeneo/php-coupling-detector/blob/master/src/Formatter/Console/PrettyFormatter.php#L81), the `` tag is not interpreted to style the output and is displayed as is.