Update bundled PSScriptAnalyzer to `v1.20.0`
See original GitHub issuePrerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
We just got PSScriptAnalzyer v1.20.0
shipped, and so should update our bundled module!
Proposed Design
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Locally installed PSScriptAnalyzer module takes precedence ...
Hm, I'm going to re-open this. For PSReadLine we decided to specifically only load the bundled copy of the module, and when we...
Read more >PSScriptAnalyzer (PSSA) 1.21.0 has been released
This minor version update includes: Three new rules; Enhances one rule; Pipeline support to Invoke-Formatter; Four bug fixes; Improved ...
Read more >How to add PowerShell linting to projects in Visual Studio Code
Step 3: Update the VSCode workspace settings. PSScriptAnalyzer is bundled with the PowerShell extension. In order to have automatic linting with ...
Read more >PowerShell editing with Visual Studio Code
The PowerShell extension includes PSScriptAnalyzer by default, ... To update Pester or to install the latest version on other platforms ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s updated in PSES, this will ship in the next preview!
Had a go at testing it end to end and looked at test cases implemented for this new config option from a community member. Although it’s an option of a ‘formatting rule’, it actually turns it out it has not materialistic impact on formatting itself. Let me explain: this PSSA setting was just added for the use case of people wanting to lint their formatting using
Invoke-ScriptAnalyzer
where 2 rule combinations were contradicting themselves. When it comes to formatting because of the magic way the formatter works (it iteratively re-runs formatting rules until it’s happy), the red herring violation from the rule shows up in the end result of the formatted string luckily. So I guess the TL;DR is that we actually do not need to expose this new setting because it would not be of any value from a formatting perspective… 😃