Skip to content

Conversation

@fm-117
Copy link
Contributor

@fm-117 fm-117 commented Dec 29, 2020

Minimal implementation of Violation concept :

  • no change in API, violations are still handled as regular diagnostics through the whole process
  • the new Violation class can be used by analyzer implementers to represent a quality rule violation
  • RuleId is transported as 'source' in LSP diagnostic object
  • all rule violations are identified by the same reserved 'code' (47)

@fm-117 fm-117 added this to the Code Quality milestone Dec 29, 2020
@fm-117 fm-117 self-assigned this Dec 29, 2020
@fm-117 fm-117 linked an issue Dec 30, 2020 that may be closed by this pull request
@fm-117 fm-117 merged commit 97936bc into 1816_NewExecutionStep_QualityCheck Jan 5, 2021
@fm-117 fm-117 deleted the 1837_AddRulesViolations branch January 5, 2021 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Rules and Violations concepts to the parser

5 participants