Better formatting for conditionals. #396
Merged
Conversation
This file contains 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
shocklateboy92
approved these changes
Aug 9, 2021
| _ => Doc.Group(Doc.Indent(Doc.Line), Doc.Indent(Node.Print(node))) | ||
| or MemberAccessExpressionSyntax | ||
| or ConditionalExpressionSyntax { Condition: BinaryExpressionSyntax | ||
| or ParenthesizedExpressionSyntax } |
There was a problem hiding this comment.
Does this have its own issue? It shouldn't be aligned with the rest, since it's nested in a sub object
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.
closes #345
This was mostly about formatting for conditionals, but ended up involving changing the logic for how assignments and variables get formatted.