-
Notifications
You must be signed in to change notification settings - Fork 191
PSScriptAnalyzer and VS Code tooling #224
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
# All default rules are also enabled. | ||
@{ | ||
Rules = @{ | ||
PSUseCompatibleSyntax = @{ |
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.
Cool!
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.
Great idea. Thanks for doing this.
One additional request before merging in.
@TylerLeonhardt - Sorry for the delay on getting this merged. If you can get the merge conflict resolved, I'll get this merged in. Thanks again for your efforts here. |
done |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
Description
This adds the following files:
launch.json
- used by vscode in order to debug PowerShellForGitHub with easePSScriptAnalyzerSettings.psd1
- used by PSSA to check syntax and also by VS Code to show problems for all rulesIssues Fixed
N/A
References
PSSA Rules: https://github.com/PowerShell/PSScriptAnalyzer/tree/master/RuleDocumentation
Specifically: https://github.com/PowerShell/PSScriptAnalyzer/blob/master/RuleDocumentation/UseCompatibleSyntax.md
Checklist
is reporting back clean.