We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
[Microsoft.Windows.PowerShell.ScriptAnalyzer.Generic.CorrectionExtent]
The text was updated successfully, but these errors were encountered:
Adding CorrectionExtent.ToString() (Fixes PowerShell#1944)
b3cdc56
e22c65f
Successfully merging a pull request may close this issue.
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.The text was updated successfully, but these errors were encountered: