-
Notifications
You must be signed in to change notification settings - Fork 382
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
Fix bug with PipelineIndentationStyle.None where break instead of continue statement was used #1497
Conversation
…tinue statement was used. TODO: Fix test that starts to fail because of this now
… into issue1496 # Conflicts: # Tests/Rules/UseConsistentIndentation.tests.ps1
Co-authored-by: Robert Holt <[email protected]>
int searchLine; | ||
do | ||
{ | ||
searchLine = tokens[searchIndex].Extent.StartLineNumber; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh! My switch
suggestion got lost! Ugh, too much context switching... Anyway, not an issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought I addressed your comment here by not initializing it: #1497 (comment)
Or did you mean a switch around tokens[searchIndex].Kind
? I don't see too much value in it tbh. Switch statements don't look that much cleaner for simple cases like that IMHO because of their ceremony that requires additional indentation layer, break statements, etc..
Otherwise we can always create a follow up PR
PR Summary
Fixes #1496
Also added another test case that would've caught it.
PR Checklist
.cs
,.ps1
and.psm1
files have the correct copyright headerWIP:
to the beginning of the title and remove the prefix when the PR is ready.