-
Notifications
You must be signed in to change notification settings - Fork 23
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
Rubocop #26
Rubocop #26
Conversation
Rubocop first pass - 5 offenses left
It might be more productive to rubocop each file rather than the entire project but Ill let you guys decide. Let me know if this works out for you. Also #25 should tell me if these changes are breaking for ruby 1.9 since I ran this rubocop on 2.2 |
This one is going to take me a bit of time to read through. Looking now. :) |
Now that you have travis, I can break it down file by file if need be and make sure each passes for different versions of ruby. I know that some of these changes will break older versions of ruby. I also added in thoughtbots rubocop config but feel free to browse through and remove/add any suggestions. |
@michaelachrisco Thanks, I looked through it and the changes all look pretty reasonable. Did they pass the tests locally? I didn't see anything that'd introduce breaking changes in my code read. Also, I am now embarrassed by my Rubies 😞 @housepage Can I get your 👀 on this too? |
Locally all the tests pass. But travis should take care of anything I am missing. 👍 |
Woot. |
Looks like 2.2 might have some issues. I would suggest not merging until #27 is passing. |
@chrismetcalf Giving this a look now. @michaelachrisco Can you can get this branch back in an automergeable state please? |
Everything looks good to me. Did the rebase, added rubocop as a dependency, added a rake task, and added it to the travis build in #30. Thanks so much for your contribution @michaelachrisco! |
Closes #24