Templates for rule descriptions #929
Description
Executable rules (i.e. constraints and concepts) should provide an optional descriptiomn templating mechanism (in addition to the rule description) supporting the following use cases:
- Rendering descriptions including values from the rule result such that each constraint violation can be reported including a full description to tools like SonarQube
- Override pre-defined descriptions (e.g. provided by rule plugins) within a project (e.g. "primary ports" vs. "incoming use case" if applying hexagonal rules to clean architecture)