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

Rm trailing whitespace in all plaintext files #350

Closed
wants to merge 2 commits into from

Conversation

evnm
Copy link

@evnm evnm commented Sep 25, 2011

Trailing whitespace makes babies cry and the Play framework is littered with it.

Removes trailing whitespace from all plaintext files within the framework. Made an effort to not include any binaries, but please advise if I've cleansed something I shouldn't have.

@hjz
Copy link

hjz commented Sep 25, 2011

LGTM. Ship it!

@hilton
Copy link

hilton commented Sep 25, 2011

Don’t do this for .textile files, where trailing whitespace is significant, signifying a continuation of a code block. Your version will have code examples where code formatting stops at the first blank line.

Trailing whitespace can be significant in textile files, signifying the
continuation of a code block.
@mbknor
Copy link
Member

mbknor commented Sep 25, 2011

Cannot merge this request.. too many changes.

You have also modified lots of "bundled" core-python files.

@mbknor mbknor closed this Sep 25, 2011
@evnm
Copy link
Author

evnm commented Sep 25, 2011

What can I do to split it up? The amount of trailing whitespace is pretty egregious.

@mbknor
Copy link
Member

mbknor commented Sep 25, 2011

you have transformed many files which are original file from other frameworks just bundled with playframework, eg:

all files under the folder 'python/' is core-python filed.. I also see that you have modified original selenium files..

also: please read the https://play.lighthouseapp.com/projects/57987/contributor-guide

@evnm
Copy link
Author

evnm commented Sep 25, 2011

Seems odd that core Python and Selenium files are included here... but I will read the guide and possibly come up with a more sensible changeset. This pull req wasn't meant as a troll. :P

Thanks for the feedback.

@mbknor
Copy link
Member

mbknor commented Sep 25, 2011

no problem at all.

Play's philosophy is to make it easy to use. Since python is not "default" on Windows, we have to bundle it..

Other stuff is also bundled for the "easy to use" reason.

Play 2.0 is not going to use any python at all..

No offense taken :)

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.

4 participants