-
Notifications
You must be signed in to change notification settings - Fork 377
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
Also return suggestion to use PSCredential for AvoidUsingPlainTextForPassword rule #1782
Also return suggestion to use PSCredential for AvoidUsingPlainTextForPassword rule #1782
Conversation
… into avoidusingplaintextforpassword-multiple-suggestions
… into avoidusingplaintextforpassword-multiple-suggestions
PR that fixes the UI bug in the extension, which only displayed one code action: PowerShell/PowerShellEditorServices#1749 |
With the recent fix in PR #1718, PSES processes now all Correction objects from PSSA but the message specifically was just taken from the last correction here. I did not notice this at first because I thought I had to tweak my rule first to emit two different messages until I realized it was another bug in PSES. Related: PowerShell/PSScriptAnalyzer#1782 Co-authored-by: Andy Schwartzmeyer <[email protected]>
@JamesWTruher Can you please help force merge it due to the old checks removed in master that are blocking the merge? |
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.
Should the severity of this rule be DiagnosticSeverity.Error
to match the severity of AvoidUsingConvertToSecureStringWithPlainText?
I think existing severities of old rules like this one are very inconsistent but my thinking is that |
PR Summary
Fixes #1767 by also adding an option for
PSCredential
.PR Checklist
.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
to the beginning of the title and remove the prefix when the PR is ready.