Skip to content

Conversation

@obrix
Copy link
Member

@obrix obrix commented Jan 29, 2026

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

No issue

What kind of change does this PR introduce?

Support the filtering option of violation condition

What is the current behavior?

Filtering attributes are ignored

What is the new behavior (if this is a feature change)?

Filtering attributes are used

Does this PR introduce a breaking change or deprecate an API?

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

Signed-off-by: Bertrand Rix <bertrand.rix@artelys.com>
@obrix obrix marked this pull request as draft January 29, 2026 15:58
@sonarqubecloud
Copy link

@obrix obrix marked this pull request as ready for review February 5, 2026 12:43
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.

1 participant