LintFormat

The matcher configuration for the lint format

This rule configures regular expressions, used to match against the output of external/3rd-party analysis tools. Using these matchers, parts of a message can be extracted and transformed into a style-violation issue.

Please refer to the documentation of the parent rulegroup for further details.

Possible Messages

This rule has no predefined messages.

Options

• This rule shares the following common options: provider

• The following places define options that affect this rule: Analysis-GlobalOptions

matchlist

matchlist

Type: bauhaus.teecap.Match | list[bauhaus.teecap.Match]

Default: [Match(regex='(?P<filename>([A-Za-z]:)?[^:]+):(?P<line>\d+):(?P<column>\d+): (?P<severity>.+) (?P<errno>\d+): (?P<message>.+)', emit=None), Match(regex='(?P<filename>([A-Za-z]:)?[^:]+):(?P<line>\d+): (?P<severity>.+): (?P<message>.+) \(PC-LINT MESSAGE NUMBER = (?P<errno>\d+)\)[\r]?', emit=None), Match(regex='Type =(?P<severity>[^ ]+) File =(?P<filename>([A-Za-z]:)?[^:]+):(?P<line>\d+):(?P<column>\d+) Nr =(?P<errno>\d+) Function\((?P<objectname>[^)]*)\) Message: (?P<message>[^\n\r]+)[\r]?', emit=None)]

The regex matcher configuration to extract the filename/line/column and message from the message from the external tool. Parts to be extracted must be specified as named capture groups. The following groupnames are supported for the transformation into a style violation issue: filename, fullname, line, column, severity, errno, objectname, message, justification