You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 likeMAJOR
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
andfail-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:
The text was updated successfully, but these errors were encountered: