-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add result.rank and ruleConfiguration.defaultRank #1167
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1306,6 +1306,13 @@ | |
] | ||
}, | ||
|
||
"rank": { | ||
"description": "A number representing the priority or importance of the result.", | ||
"type":"number", | ||
"minimum": 0.0, | ||
"maximum": 100.0 | ||
}, | ||
|
||
"attachments": { | ||
"description": "A set of files relevant to the result.", | ||
"type": "array", | ||
|
@@ -1438,11 +1445,19 @@ | |
}, | ||
|
||
"defaultLevel": { | ||
"description": "Specifies the default severity level of the result.", | ||
"description": "Specifies the default severity level for results generated by this rule.", | ||
"default": "warning", | ||
"enum": [ "note", "warning", "error" ] | ||
}, | ||
|
||
"defaultRank": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
my apologies. I have, yet again, completely misunderstood your proposal in context of the TC. I never thought we were applying a defaultRank to a rule. This doesn't make sense: ranks are generally computed values that are applied to all results. Ranks are generally available or not. when you discussed a default rank, I thought you are asking 'what is the default value of result.rank' if it isn't explicit? in this case, i have argued that the default s/be 0. so what I expected in this case was that we would not have a new ruleConfiguration property but we would have another explanatory sentence in the spec. |
||
"description": "Specifies the default priority or importance for results generated by this rule.", | ||
"type":"number", | ||
"minimum": 0.0, | ||
"maximum": 100.0, | ||
"default": 0.0 | ||
}, | ||
|
||
"parameters": { | ||
"description": "Contains configuration information specific to this rule.", | ||
"$ref": "#/definitions/propertyBag" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you need this? are you comfortable deleting 'or importance'? importance is a slippery slope that pulls in the severity of vulns, the level of exposure, etc. rank is a relative ordering. i think 'priority' sufficiently communicates what we're after.