Skip to content
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

Add a rule about a newline at eof #287

Merged
merged 1 commit into from
Feb 17, 2014

Conversation

phts
Copy link
Contributor

@phts phts commented Feb 16, 2014

@bbatsov
Copy link
Collaborator

bbatsov commented Feb 16, 2014

Source files should end with a newline, not a blank line.

@phts
Copy link
Contributor Author

phts commented Feb 17, 2014

@bbatsov agreed. I've fixed this rule

@bbatsov
Copy link
Collaborator

bbatsov commented Feb 17, 2014

@phts Looks good. Please, squash the two commits into one.

@phts
Copy link
Contributor Author

phts commented Feb 17, 2014

@bbatsov Done

bbatsov added a commit that referenced this pull request Feb 17, 2014
Add a rule about a newline at eof
@bbatsov bbatsov merged commit 7736f37 into rubocop:master Feb 17, 2014
@bbatsov
Copy link
Collaborator

bbatsov commented Feb 17, 2014

Thanks.

@gnapse
Copy link
Contributor

gnapse commented Apr 24, 2014

I do agree with this rule 100%, but I would like to know the why.

In my case I consider it beneficial because it leads to cleaner diffs in version control systems. But that reason does not seem to be good enough for other rules that have been suggested but not yet accepted (such as trailing commas in multi-line array literals, like #273 and #290).

So clearly, there could be other reasons aside from the VCS argument. If so, which are they?

marocchino pushed a commit to marocchino/ruby-style-guide that referenced this pull request Aug 11, 2015
shyouhei pushed a commit to shyouhei/ruby-style-guide that referenced this pull request Nov 11, 2015
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.

3 participants