-
Notifications
You must be signed in to change notification settings - Fork 94
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
Fix Ruby 2.7 warnings on Proc.new #90
Conversation
Referenced this in my Gemfile and ran tests. Warnings are gone and my tests stayed green. |
Same here, all green, thanks for the job done ✌️ |
@jenseng Could you merge this and release a new version please? Thanks! 🙇 |
Any update @jenseng :) ? |
@jenseng It would be great to have this in a new version 🙏 |
Calling Error:
@jenseng Could you please merge this and release as a new version? Thank you! |
Hi guys, I see @jenseng is not responding and last commit in master is since Sep 2019. Do you think this repo is abandoned and we should do our own fork? It's unfortunate, since it looked like a solid gem :'( |
👋 sorry everyone, my github notifications were off and I haven't been using this gem (or even ruby) in years 😬 ... I'll get these merged and released shortly, but if anyone wants to help take over maintaining this gem moving forward I'm totally open to it 🤗 |
released in v0.2.24 |
This fixes issue #89 Ruby 2.7 gives warning on use of Proc.new:
hair_trigger/builder.rb:145: warning: Capturing the given block using Proc.new is deprecated; use &blockinstead hair_trigger/builder.rb:155: warning: Capturing the given block using Proc.new is deprecated; use&block instead