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

Rubocop 0.37.2 #44

Closed
3 tasks done
nijikon opened this issue Jan 17, 2016 · 4 comments
Closed
3 tasks done

Rubocop 0.37.2 #44

nijikon opened this issue Jan 17, 2016 · 4 comments
Assignees

Comments

@nijikon
Copy link
Contributor

nijikon commented Jan 17, 2016

In order for us to upgrade to rubocop 0.37.1, this things need to happen

@nijikon nijikon self-assigned this Jan 17, 2016
@chastell
Copy link

Just to let you know: using RuboCop 0.36 along Reek is blocked because RuboCop (rightly so) depends on parser >= 2.3.0.1 while Reek depends on unparser which depends on parser ~> 2.2.2. Bumping unparser’s dependency probably won’t happen soon, so we’re working on dropping unparser, but it will take us a bit. Sorry!

@nijikon
Copy link
Contributor Author

nijikon commented Jan 18, 2016

@chastell Yes I did noticed that, I will monitor the other issue, thanks!

@chastell
Copy link

We’ve released Reek 3.9.0, which at least bumps the Parser dependency so you can use Reek and newest RuboCop together. :)

@nijikon
Copy link
Contributor Author

nijikon commented Jan 22, 2016

Yup, I noticed that thanks! Waiting for rubycritic to bump it to reek 3.9.0 :)

@nijikon nijikon changed the title Rubocop 0.36.0 Rubocop 0.37.1 Feb 9, 2016
@nijikon nijikon changed the title Rubocop 0.37.1 Rubocop 0.37.2 Feb 18, 2016
@nijikon nijikon closed this as completed in 521c381 Mar 3, 2016
nijikon added a commit that referenced this issue Mar 3, 2016
rubocop 0.37.2, rubocop-rspec 1.4.0, rubycritic 2.7.1, Fixes #44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants