Change default of powershell.codeFormatting.pipelineIndentationStyle from None back to NoIndentation due to PSSA bug #2698
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Fixes #2696
cc @TylerLeonhardt @rjmholt
Tracking PSSA bug is here: PowerShell/PSScriptAnalyzer#1496
I already have a fix ready for the PSSA issue, it is an embarrassing mistake, I used
break
when I meant to usecontinue
in a for loop :-(Sorry, but without the test coverage from the preview extension, I wouldn't have found this earlier because locally I don't use the default value for that setting.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
x
between the square brackets.Please mark anything not applicable to this PR
NA
.WIP:
to the beginning of the title and remove the prefix when the PR is ready