-
Notifications
You must be signed in to change notification settings - Fork 395
PSScriptAnalyzer rule documentation files should be named consistently with the rules #736
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
Comments
The rule documentation files are here, just look for the filename without the PS prefix: https://github.com/PowerShell/PSScriptAnalyzer/tree/development/RuleDocumentation |
Interesting. The documentation there doesn't cover PSAvoidShouldContinueWithoutForce or AvoidUsingCmdletAliases - both of which are in the VSCode addon (v0.10.1) Is there some renaming going on between VSCode and PSScriptAnalyzer? Or is VSCode just running behind on the version of PSScriptAnalyzer it uses? |
I think the documentation could be a little out of date, the PowerShell extension is using 1.11.0 of PSScriptAnalyzer. The AvoidUsingCmdletAliases documentation is here: The PSAvoidShouldContinueWithoutForce is here, but it's named without the PS: We definitely need to do a review to make sure the documentation naming is correct. |
This is a dup of #729. |
Fixed in #742 |
I'n using PSScriptAnalyzer from inside VSCode, and there doesn't seem to be any documentation of what each rule does, which makes it very hard to decide whether to enable one or not.
Is there a page somewhere which tells me what (for instance) PSAvoidShouldContinueWithoutForce means, so that I can make an informed decision whether to enable that rule?
The text was updated successfully, but these errors were encountered: