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

tabs to spaces and use 2space indenting #1384

Merged
merged 3 commits into from Apr 29, 2016

Conversation

Projects
None yet
4 participants
@connortechnology
Member

connortechnology commented Apr 4, 2016

step 1 of following google code guidelines. This is just the files in /src so far.

@kylejohnson

This comment has been minimized.

Show comment
Hide comment
@kylejohnson

kylejohnson Apr 4, 2016

Member

So, 👍 on putting this in its own PR!

Anyway, the google doc says this:

Use only spaces, and indent 2 spaces at a time.

We use spaces for indentation. Do not use tabs in your code. You should set your editor to emit spaces when you hit the tab key.

That's just their standard, with no information on why.

While I do agree that our code is a mess of uneven tabs and spacing, why do you think we should go with spaces (over tabs)?

Would we then reject PRs down the line which use tabs over spaces? (I'd say yes)

Member

kylejohnson commented Apr 4, 2016

So, 👍 on putting this in its own PR!

Anyway, the google doc says this:

Use only spaces, and indent 2 spaces at a time.

We use spaces for indentation. Do not use tabs in your code. You should set your editor to emit spaces when you hit the tab key.

That's just their standard, with no information on why.

While I do agree that our code is a mess of uneven tabs and spacing, why do you think we should go with spaces (over tabs)?

Would we then reject PRs down the line which use tabs over spaces? (I'd say yes)

@connortechnology

This comment has been minimized.

Show comment
Hide comment
@connortechnology

connortechnology Apr 4, 2016

Member

Yeah we need to force people to follow the coding style.

Member

connortechnology commented Apr 4, 2016

Yeah we need to force people to follow the coding style.

@Linwood-F

This comment has been minimized.

Show comment
Hide comment
@Linwood-F

Linwood-F Apr 4, 2016

Contributor

Just in the FWIW department, tabs are not always interpreted the same in different IDE's, and often "move" after a copy/paste; spaces are uniform in how they are handled.

Contributor

Linwood-F commented Apr 4, 2016

Just in the FWIW department, tabs are not always interpreted the same in different IDE's, and often "move" after a copy/paste; spaces are uniform in how they are handled.

@kylejohnson

This comment has been minimized.

Show comment
Hide comment
@kylejohnson

kylejohnson Apr 4, 2016

Member

Just in the FWIW department, tabs are not always interpreted the same in different IDE's, and often "move" after a copy/paste; spaces are uniform in how they are handled.

Now that's a good reason.

Member

kylejohnson commented Apr 4, 2016

Just in the FWIW department, tabs are not always interpreted the same in different IDE's, and often "move" after a copy/paste; spaces are uniform in how they are handled.

Now that's a good reason.

connortechnology added some commits Apr 28, 2016

@SteveGilvarry SteveGilvarry merged commit 66a3fef into master Apr 29, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment