Fix PlaceCloseBrace rule behavior for NewLineAfter switch #781
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 11 commits
June 11, 2017 20:18
Whenever `NewLineAfter = $false`, the rule creates a violation if a branching statement is on a new line after the preceding close brace. We consider the following braching statements: - else - elseif - catch - finally
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prior to the fix, whenever the user sets
NewLineAfter = $false, the rule would ignore instances where a new line would follow a close brace. With this PR, whenveerNewLineAfter = $false, the rule enforces no new line after close braces that are followed branching statements. This would provide the ability to cuddle the following statements: