-
Notifications
You must be signed in to change notification settings - Fork 395
Rule to validate the presence of Verbose statements in DSC Resource #238
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
Conversation
{ | ||
return AstVisitAction.Continue; | ||
} | ||
List<string> expectedTargetResourceFunctionNames = new List<string>(new string[] { "Set-TargetResource", "Test-TargetResource", "Get-TargetResource" }); |
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.
I don't think we use this anywhere in the code?
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.
Quoc. I did not understand your comment.
Since this rule is enabled only for cmdlet based DSC resources, we do not need to validate for advanced functions...
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.
Oh I mean the DscResourceFunctions in the Helper class already takes out the set, get and test targetresource functions. Also what I mean is we didn't use the variable expectedTargetResourceFunctionNames anywhere in this file?
good catch. Updated the pull request with changes |
Looks good to me. |
thanks. I will merge once Appveyor is clean |
…ranch Rule to validate the presence of Verbose statements in DSC Resource
No description provided.