8000 Add configs of rubocop gem and fix some rubocop warnings by ShockwaveNN · Pull Request #226 · rubyzip/rubyzip · GitHub
[go: up one dir, main page]

Skip to content

Add configs of rubocop gem and fix some rubocop warnings #226

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

Merged
merged 107 commits into from
Jun 8, 2015
Merged

Add configs of rubocop gem and fix some rubocop warnings #226

merged 107 commits into from
Jun 8, 2015

Conversation

ShockwaveNN
Copy link
Contributor

I run rubocop (https://github.com/bbatsov/rubocop) gem on this project and fix some of problem to try it out.
If maintainers of this project think this is good idea - I can continue to fix code style warnings and creating pull requests for it

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0%) to 93.39% when pulling 7a8a8b6 on ShockwaveNN:rubocop_fixes into 4698e57 on rubyzip:master.

@simonoff
Copy link
Member

@ShockwaveNN If you have a time then ok. But rubocop is not enough. You can look on reek and cane.

@@ -0,0 +1,2 @@
inherit_from:
- .rubocop_todo.yml
Copy link
Member

Choose a reason for hiding this comment

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

Please rename file to .rubocop_rubyzip.yml

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Are you sure about it?
Without renaming I can just run rubocop command from root of project and it will use this config file, but if i rename - I should run rubocop -c .rubocop_rubyzip.yml

Copy link
Member

Choose a reason for hiding this comment

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

Why? you renaming file and renaming entry in .rubocop.yml

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I get it. I thought you mention .rubocop.yml file, but you mention .rubocop_todo.yml file

@ShockwaveNN
Copy link
Contributor Author

I fixed some trivial problems, I stop now, but try to continue tomorrow

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0%) to 93.39% when pulling f401fff on ShockwaveNN:rubocop_fixes into 4698e57 on rubyzip:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.26%) to 93.65% when pulling e211434 on ShockwaveNN:rubocop_fixes into 4698e57 on rubyzip:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.26%) to 93.65% when pulling e211434 on ShockwaveNN:rubocop_fixes into 4698e57 on rubyzip:master.

@ShockwaveNN
Copy link
Contributor Author

I think I fixed almost all trivial cases, so I think it may be merged with master, because after that point fixes will be more dramatical, and may be lost in existing changes. Existing changes is small, but there is too much number of them. Also future fixes volumes will not be so high, as now

@simonoff
Copy link
Member
simonoff commented Jun 6, 2015

Can you rebase with latest master?

@ShockwaveNN
Copy link
Contributor Author

@simonoff Yes, of course I can rebase. I try to do it tomorrow

@ShockwaveNN
Copy link
Contributor Author

@simonoff Done rebasing, also update rubocop and fix some more problems

simonoff added a commit that referenced this pull request Jun 8, 2015
Add configs of rubocop gem and fix some rubocop warnings
@simonoff simonoff merged commit bbd7cc4 into rubyzip:master Jun 8, 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.

4 participants
0