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
As custom rules are not contained in the default ruleset, the rule definition is nil.
This has the effect that the function for getting rules by category will exclude the results for custom rules by checking that the rule must not be nil.
I guess one option could be to put the ruleset used for creating the report into the report as well. Another one to let the user hand in the same ruleset again when creating the html-report and reading from the vacuum report file. (although that feels strange)
The text was updated successfully, but these errors were encountered:
When creating an html-report from a vacuum report, the html page only contains results for the default rules.
This is because when re-creating the nodes from the report data, the rule data is taken from the OpenAPIDefaultRuleSet and retrieved via the rule-id..
As custom rules are not contained in the default ruleset, the rule definition is nil.
This has the effect that the function for getting rules by category will exclude the results for custom rules by checking that the rule must not be nil.
I guess one option could be to put the ruleset used for creating the report into the report as well. Another one to let the user hand in the same ruleset again when creating the html-report and reading from the vacuum report file. (although that feels strange)
The text was updated successfully, but these errors were encountered: