Skip to content

Conversation

@dsyme
Copy link
Contributor

@dsyme dsyme commented Mar 21, 2019

More bike shedding in the morning.

This is all whitespace cleanup.

Why use one space when we could randomly scatter multiple spaces throughout our codebase?

@dsyme
Copy link
Contributor Author

dsyme commented Mar 21, 2019

Ugh, this test is still flaky:


Failed   TypeProvider.Disposal.SmokeTest2
Error Message:
   Check6b, at end, countCreations() = countDisposals() after explicit clearing
  Expected: True
  But was:  False

Stack Trace:
   at Tests.LanguageService.Script.UsingMSBuild.TypeProviderDisposalSmokeTest(Boolean clearing) in D:\a\1\s\vsintegration\tests\UnitTests\LegacyLanguageService\Tests.LanguageService.Script.fs:line 1662
   at Tests.LanguageService.Script.UsingMSBuild.TypeProvider.Disposal.SmokeTest2() in D:\a\1\s\vsintegration\tests\UnitTests\LegacyLanguageService\Tests.LanguageService.Script.fs:line 1670

@dsyme dsyme closed this Mar 21, 2019
@dsyme dsyme reopened this Mar 21, 2019
@KevinRansom
Copy link
Contributor

While doing this can you get rid of the random whitespace at the end of lines. Because that triggers my OCD big time.

@baronfel
Copy link
Member

baronfel commented Mar 21, 2019

If we put an .editorconfig in the repo root with the correct configuration, most editors these days will enforce constraints like 'trim spaces at end of line' and 'newline at end of file'. Might be a simple way to bring the repo into alignment and ensure consistency going forward.

@dsyme
Copy link
Contributor Author

dsyme commented Mar 21, 2019

While doing this can you get rid of the random whitespace at the end of lines. Because that triggers my OCD big time.

Let's do that in a separate PR, once for all.

@NatElkins
Copy link
Contributor

If you do end up doing it, I added a test for trailing whitespace a long time ago which could probably be re-added: #1421

@dsyme
Copy link
Contributor Author

dsyme commented Mar 21, 2019

@NatElkins Thanks!

@TIHan or @KevinRansom , can you approve then we can get about integrating this into PRs etc.? thanks

@BentTranberg
Copy link

<rant> I don't understand why VS don't strip whitespace from the end of lines and end of files. I have complained to MS about this many times through the years, to no avail. I don't remember having used any other code editor that lacks this feature. In large teams this is essential to prevent many meaningless changes in commits, and it is a nuisance to have to ask the entire team to install extensions for such basic functionality. </rant>

@dsyme
Copy link
Contributor Author

dsyme commented Mar 22, 2019

@TIHan or @KevinRansom , can you approve then we can get about integrating this into PRs etc.? thanks

Ping :) the longer we leave it dangling the more integration pain we get :)

Copy link
Contributor

@TIHan TIHan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems simple enough. Nothing glaring from my point of view.

@dsyme dsyme merged commit 87cbf6f into dotnet:master Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants