-
Notifications
You must be signed in to change notification settings - Fork 240
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
Guard::RSpec::Formatter formatter with deprecated interface #253
Comments
@907th what do you think to have one formatter per rspec versions (2.14 & 3.0) ? |
@thibaudgg I may take a look at it later. Will we continue to support both rspec versions in one guard-rspec branch? |
Yeah, as long that 2.14 is the most used version, I think it's a good idea to support both. Do you agree? |
Yes, I agree. I mean that one day it would become difficult to maintain a code for both versions in the same place. |
@907th sure, once RSpec 3.0 usage will be well established, we will drop 2.14 support! |
In the meantime, do you know of a way to turn off this deprecation message? |
@leifg No, I don't. I will have a time to watch at it in the end of the week only. If you know how to resolve this - PR is welcome! ) |
@907th Deprecation messages really annoy me, so I've submitted a PR that fixes the issue! Let me know if there's anything I should tidy up. :) |
v4.2.8 with fix by @wless1 released |
Thanks all! |
I'm still seeing this error. Is the Github repo synchronizd with the rubygems? |
Never mind. It was a problem on my end. |
I've been getting this message just as a heads up. Not emergent obviously.
The text was updated successfully, but these errors were encountered: