Open rkeithhill opened 9 years ago
Another option for the category parameter for built-in rules could be:
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSScriptAnalyzer.PS", "PSProvideDefaultParameterValue", MessageId="a")]
[Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSScriptAnalyzer.PSDSC", "PSDSCDscTestsPresent")]
Keith. Thanks for your input.
This is a feature request and we will add to the backlog items
So here is an example of how PSScriptAnalyzer is using this attribute to target a parameter:
But the intent of the first two parameters of the SuppressMessageAttribute constructor are to uniquely identify the suppressed rule, and to apply to a parameter would use the MessageId property e.g.:
So I would expect that every PowerShell suppression of a built-in rule would start like this:
This identifies the rule as a built-in rule. I could imagine custom rules would use their module/assembly name in the first field (category).
Suppression of a parameter should look like:
Note that MessageId is the field that is supposed to be used if Scope/Target aren't sufficiently precise.