What "patterns & principles" should be included? #2
Description
One of the forms of situational expression is the tagging of various patterns and principles. Sometimes they can be use to simplify the message to convey or help point the developer who will address it to something they should learn about or rethink first.
For example: [SideEffects(solid: Solid.SingleResponsibility)]
The options are grouped and isolated to support bitwise stacking of multiple enum values. Names are preferred in long form to ensure readability. For example, SRP may be well known to the reviewer but not so much for the developer having to do something about it.
The items currently included can be found in the link below which are only a conversational starter.
https://github.com/rskopecek/CodeDocs/tree/master/src/CodeDocs/PatternsAndPrinciples