-
Notifications
You must be signed in to change notification settings - Fork 269
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: Format for comprehension expressions #3916
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
561a047
Fix: Format for comprehension expressions
MikaelMayer fa854e7
added comment
MikaelMayer 900c92d
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer 298ada2
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer f741cae
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer 174f2ed
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer c2a922d
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer 0359477
Update FormatterIssues.cs
MikaelMayer 5ee8262
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer e556819
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer f324fb1
Merge branch 'master' into fix-3912-formatter-collection-arrow
MikaelMayer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Format for comprehension expressions |
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.
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.
Is this
PartE
intended to be aligned withPartD
, or is it supposed to be one 2-space indent past the corresponding<-
?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.
It is intended to be aligned with PartD. Specifically, the "<-" is treated like an "in" binary operator, and I put the rule that if the "in" operator is not followed by a newline, then it starts a new aligning indentation. If it is followed by a newline, then it's indented by two spaces as usual. This matches usages of newlines I've seen for the second argument of "in" and "<-"