Skip to content

Commit ac0af3e

Browse files
committed
results: set the "imp" flag in the list of important findings
... rather than clearing it. If scan results are processed later on, it is useful to know the original state of the "imp" flag, regardless of the context (whether we have a list of important findings only, or an all-in-one list of findings). A side effect will be that a red `[important]` tag will appear in the HTML output next to each finding, which is probably harmless. Related: https://issues.redhat.com/browse/OSH-343 Related: https://issues.redhat.com/browse/OSH-565 Closes: #159
1 parent 154cf56 commit ac0af3e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

py/common/results.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -314,7 +314,7 @@ def finalize_results(js_file, results, props):
314314
% (js_file, chk_re, csgrep_args)
315315

316316
# finally take all defects that were tagged important by the scanner already
317-
cmd += " | csgrep --mode=json --set-imp-level=0 --remove-duplicates"
317+
cmd += " | csgrep --mode=json --set-imp-level=1 --remove-duplicates"
318318
cmd += f" <(csgrep --mode=json --imp-level=1 '{js_file}') -"
319319

320320
# write the result into *-imp.js

0 commit comments

Comments
 (0)