Skip to content

CorrectionExtent should support .ToString() #1944

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

Closed
StartAutomating opened this issue Oct 10, 2023 · 0 comments · Fixed by #1946
Closed

CorrectionExtent should support .ToString() #1944

StartAutomating opened this issue Oct 10, 2023 · 0 comments · Fixed by #1946
Milestone

Comments

@StartAutomating
Copy link
Contributor

Summary of the new feature

Script Analyzer rule connections use the default ToString(), which merely displays the type.

This means that to test the result of a script analyzer rule with a regex, one needs to dig into subproperties.

It also means that, say, a list of corrections in a CSV will simply look broken.

Proposed technical implementation details (optional)

[Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.CorrectionExtent] should override .ToString() method to output the correction string.

@StartAutomating StartAutomating changed the title SuggestedCorrections should support .ToString() CorrectionExtent should support .ToString() Oct 10, 2023
StartAutomating pushed a commit to StartAutomating/PSScriptAnalyzer that referenced this issue Oct 10, 2023
@SydneyhSmith SydneyhSmith added this to the 1.22 milestone Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants