Fixup whitespace and new lines in Common props, targets and tasks #6159
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
only in MSBuild Common props, targets and tasks files Conforming to the repository's EditorConfig file
only in MSBuild Common props, targets and tasks files Add New Line(s) between every block to make it clear. Remove unnecessary New Line(s) to reduce scrolling.
Nirmal4G
changed the title
KirillOsenkov
approved these changes
Feb 19, 2021
Forgind
approved these changes
Mar 1, 2021
Forgind
added
the
merge-when-branch-open
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.
Part of #4779
Context
Make Common props, targets and tasks easier to read and understand.
Fixup whitespace and new lines only in Common props, targets and tasks files.
Part of the larger refactoring that'll lead into #1686
Changes Made
Notes
I'll also make sure not to mess up the git blame too much.
To make reviewing easier, I had split up the changes logically rather than a file.
Also, please do note that these changes won't make much difference alone but with other formatting and refactors that follow this will make a world of difference in reading these files.