A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/pmd/pmd/issues/5525 below:

[core] Add rule priority as level to Sarif report · Issue #5525 · pmd/pmd · GitHub

PMD doesn't include a level of severity in their sarif-report, so a user has no feedback on how severe the found error actually is.
Spotbug, for example, fills the level property for each bug. PMD already defines priorities for their rules, so maybe that can simply be used for this property.
I think this would be an helpful addition, and a quick fix. Let me know if there are reasons why not to do this!

The rule priority should be added in two places:

  1. as a default value for the rule's reportingDescriptor:
    sarifLog -> runs[] -> tool -> driver -> rules[] -> defaultConfiguration -> level="warning"|"error"|"note"|"none"
    This corresponds to 3.50.3 level property

  2. as a concrete value for inside each result object:
    sarifLog -> runs[] -> results[] -> level="warning"|"error"|"note"|"none"
    This corresponds to: 3.27.10 level property


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4