Skip to content
This repository was archived by the owner on Feb 28, 2024. It is now read-only.

Conversation

@zkxs
Copy link
Collaborator

@zkxs zkxs commented Aug 19, 2022

Changes everything to two spaces. Removes human-readable whitespace guidelines from CONTRIBUTING.md as they are superseded by editorconfig.

dotnet format doesn't run on csproj or sln files so I've formatted them manually.

THE PRS WILL CONTINUE
UNTIL MORALE IMPROVES

@zkxs zkxs requested review from EIA485 and l-2-j August 19, 2022 20:34
@zkxs zkxs mentioned this pull request Aug 19, 2022
@EIA485
Copy link
Member

EIA485 commented Aug 19, 2022

personally i prefer 4 spaces, curios why we are changing it.

@zkxs
Copy link
Collaborator Author

zkxs commented Aug 19, 2022

I personally don't care one way or the other as long as we're consistent. And I'm not really a C# guy so I don't know what the meta is.

@XDelta
Copy link
Member

XDelta commented Aug 19, 2022

I'd agree on 4 spaces

@EIA485
Copy link
Member

EIA485 commented Aug 19, 2022

ive opened pr #63 to update the editor config to match the current contributing.md

@l-2-j
Copy link
Member

l-2-j commented Aug 20, 2022

Okay so iirc I just quickly looked at the csproj files, saw 2 spaces, and went "oh okay this is what's been used" without properly checking the cs files x'D the end_of_line = lf was intentional, having files which aren't that wasn't.

Comment on lines 19 to 28
- *.cs files
- Lines MUST be indented using four spaces. Tabs are not acceptable.
- Lines MUST be indented using two spaces. Tabs are not acceptable.
- MUST use unix-style (LF) line endings. CR or CRLF are not acceptable.
- *.sln files: use the Visual Studio defaults
- indent using tabs
- *.sln files
- indent using two spaces
- CRLF line endings
- *.csproj files: use the Visual Studio defaults
- *.csproj files
- indent using two spaces
- CRLF line endings

Copy link
Member

@l-2-j l-2-j Aug 20, 2022

Choose a reason for hiding this comment

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

.... I really want to have one unified style for everything instead of 3 different ones though.

@zkxs zkxs changed the title Update contributing.md to match editorconfig What if we used 2 spaces, though? Aug 20, 2022
@zkxs
Copy link
Collaborator Author

zkxs commented Aug 20, 2022

*.csproj and *.sln are now formatted using 2 spaces and LF. I've removed human-readable whitespace guidelines from CONTRIBUTING.md as they are superseded by editorconfig.

This brings the PR in line with tab and 4-space PRs, so I've edited the title and description to match.

Copy link
Member

@l-2-j l-2-j left a comment

Choose a reason for hiding this comment

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

I mean, I can also agree on 2 spaces since it's not as big as 4, and what I've configured my tab size as

@EIA485
Copy link
Member

EIA485 commented Aug 20, 2022

#65 seems to be the best option as it allows you to change the visual based on your preference within your editor

@zkxs
Copy link
Collaborator Author

zkxs commented Aug 20, 2022

#65 is the ultimate winner.

@zkxs zkxs closed this Aug 20, 2022
@EIA485 EIA485 deleted the 2-space-gang branch August 22, 2022 23:04
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants