# This file defines the tags available to analyzers when creating issues.
# An issue can have any number of tags, and each tag consists of one or
# more arbitrary values. The tags don't affect the analyzers internally,
# but they can affect the output of the report generated by dmu-analyze
# so that developers can peruse their modules' issues in various ways.
#
# See hasTag(), getTag(), setTag(), and clearTag() in IssueInterface.

definitions:
  # Categories for issues. An issue can be in any number of categories.
  # Categories are tagged by their machine name, so that the human-readable
  # title is editable in one place (namely, here).
  category:
    block: 'Blocks'
    cache: 'Caching'
    config: 'Configuration'
    ctools: 'CTools'
    db: 'Database'
    entity: 'Entity API'
    field: 'Field API'
    form: 'Form API'
    info: 'Info File'
    menu: 'Menu/Routing'
    misc: 'Miscellaneous'
    node: 'Node API'
    render: 'Rendering'
    system: 'System'
    taxonomy: 'Taxonomy'
    theme: 'Theme System'
    ui: 'User Interface'
    user: 'Users'
    utility: 'Utilities'

  # Issue error levels. At the time of this writing, all this affects is
  # the CSS class of the issue as rendered in the report.
  error_level:
    - error
    - warning