Skip to content

Fix severity inconsistency in AvoidUsingConvertToSecureStringWithPlainText #470

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

Merged
merged 6 commits into from
Mar 21, 2016

Conversation

kapilmb
Copy link

@kapilmb kapilmb commented Mar 17, 2016

This change is Reviewable

Kapil Borle added 2 commits March 16, 2016 15:12
…PlainText rule.

The severity showed by Get-ScriptAnalyzerRule and Invoke-ScriptAnalyzer for this rule were different. This
was because scriptanalyzer defines two types of severities, viz., RuleSeverity and DiagnosticSeverity and
the severity levels were not consistent.

This commit makes the severity level consistent by setting them both to Warning.
@raghushantha
Copy link
Member

a discussion (no related file):
Are all the built-in rules consistent in terms of Severity emitted by GetSeverity() vs Diagnostic record?


Comments from the review on Reviewable.io

@raghushantha
Copy link
Member

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


Comments from the review on Reviewable.io

@raghushantha
Copy link
Member

:lgtm:


Comments from the review on Reviewable.io

@raghushantha
Copy link
Member

Reviewed 9 of 9 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


Comments from the review on Reviewable.io

@raghushantha
Copy link
Member

Review status: all files reviewed at latest revision, all discussions resolved.


a discussion (no related file):
changes are good


Comments from the review on Reviewable.io

kapilmb pushed a commit that referenced this pull request Mar 21, 2016
Fix severity inconsistency in AvoidUsingConvertToSecureStringWithPlainText and UseIdenticalParametersDSC
@kapilmb kapilmb merged commit 6b51b94 into development Mar 21, 2016
@kapilmb kapilmb deleted the FixSeverityInconsistency branch March 21, 2016 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants