1 # This file defines the tags available to analyzers when creating issues.
2 # An issue can have any number of tags, and each tag consists of one or
3 # more arbitrary values. The tags don't affect the analyzers internally,
4 # but they can affect the output of the report generated by dmu-analyze
5 # so that developers can peruse their modules' issues in various ways.
7 # See hasTag(), getTag(), setTag(), and clearTag() in IssueInterface.
10 # Categories for issues. An issue can be in any number of categories.
11 # Categories are tagged by their machine name, so that the human-readable
12 # title is editable in one place (namely, here).
16 config: 'Configuration'
34 # Issue error levels. At the time of this writing, all this affects is
35 # the CSS class of the issue as rendered in the report.