Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Group/Rule-wise Configuration of Warning/Failure Thresholds #820

Open
SebastianWendorf opened this issue Feb 24, 2025 · 0 comments
Milestone

Comments

@SebastianWendorf
Copy link
Contributor

Currently it is possible to define a general severity at which a warning/failure during the jQA analysis should occur. This is done via the jqassistant.analyze.report.warn-on-severity and .fail-on-severity configuration properties, where a concrete severity value like MAJOR can be set.

To allow more fine-tuned configuration possibilities it would be good to override the general thresholds described above with group/rule-wise thresholds.

In addition to the current configuration mode, it should be possible to define the warn-on-severity and fail-on-severity as YAML mappings with the "*" key to set the default value and concrete rule/group names as keys for partial overrides of the default value. The use of wildcards should be allowed for the description of rule names.

Example:

jqassistant:
  # ...
  analyze:
    report:
      warn-on-severity:
        "*": MAJOR
        "my-important-group": MINOR
        "spring:*": CRITICAL
      fail-on-severity:
        "*": CRITICAL
        "my-important-group": MAJOR
        "spring:*": BLOCKER
@DirkMahler DirkMahler added this to the 3.0 milestone Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants