-
Notifications
You must be signed in to change notification settings - Fork 33
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
Is there a blocker on using the new ruby_parser (not locking the gem at ~>2.3)? #15
Comments
What version are you trying to get to... I just tried updating all the way to the latest, and noticed that causes errors with the current code. I could likely fix the code and update to a newer version, just not sure who might care about the old versions, but I guess they could just use the old version of churn if they needed. I would be happy to update, if it makes it more compatible with some of the other metric tools. It looks like the break occurs when moving from sexp 4.0.X to 4.1.0, so you basically just want me to do full version bumps gem.add_dependency "sexp_processor", ' I likely won't have time to fix this until the weekend...
|
Thanks for looking at that. I'm working on https://github.com/metricfu/metric_fu and want to 'put the band back together', which includes updating the dependencies of the dependencies, and it looks like you're still actively developing on this. I don't know if it might be helpful, but the brakeman project has a ruby_parser / sexp_processor compatibility layer. (written before ruby_parser reach full 1.9 compliance in the 3.0 release) |
Cool I will look at the brakeman project. I figured this was for metric_fu updates. Very cool that you are working on that. I will dig in a bit this weekend and hopefully get a gem update released for you. peace, |
OK so I bumped the version of churn and updated the ruby_parser and sexp_processor dependancies https://rubygems.org/gems/churn Let me know if any of the other old gems are causing issues. |
Is there a blocker on using the new ruby_parser (not locking the gem at ~>2.3)?
The text was updated successfully, but these errors were encountered: