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

Guard::RSpec::Formatter formatter with deprecated interface #253

Closed
mtobias opened this issue Feb 24, 2014 · 12 comments · Fixed by #254
Closed

Guard::RSpec::Formatter formatter with deprecated interface #253

mtobias opened this issue Feb 24, 2014 · 12 comments · Fixed by #254

Comments

@mtobias
Copy link

mtobias commented Feb 24, 2014

I've been getting this message just as a heads up. Not emergent obviously.

The Guard::RSpec::Formatter formatter uses the deprecated formatter interface.
 Formatter added at: /Users/x/.rvm/gems/ruby-2.0.0-p353/gems/rspec-core-3.0.0.beta2/exe/rspec:4:in `<top (required)>'
@thibaudgg
Copy link
Member

@907th what do you think to have one formatter per rspec versions (2.14 & 3.0) ?

@907th
Copy link
Contributor

907th commented Feb 25, 2014

@thibaudgg I may take a look at it later. Will we continue to support both rspec versions in one guard-rspec branch?

@thibaudgg
Copy link
Member

Yeah, as long that 2.14 is the most used version, I think it's a good idea to support both. Do you agree?

@907th
Copy link
Contributor

907th commented Feb 25, 2014

Yes, I agree. I mean that one day it would become difficult to maintain a code for both versions in the same place.

@thibaudgg
Copy link
Member

@907th sure, once RSpec 3.0 usage will be well established, we will drop 2.14 support!

@leifg
Copy link

leifg commented Mar 3, 2014

In the meantime, do you know of a way to turn off this deprecation message?

@907th
Copy link
Contributor

907th commented Mar 3, 2014

@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! )

@tokafish
Copy link
Contributor

tokafish commented Mar 4, 2014

@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. :)

@907th 907th closed this as completed in #254 Mar 5, 2014
@907th
Copy link
Contributor

907th commented Mar 5, 2014

v4.2.8 with fix by @wless1 released

@thibaudgg
Copy link
Member

Thanks all!

@volkanunsal
Copy link

I'm still seeing this error. Is the Github repo synchronizd with the rubygems?

@volkanunsal
Copy link

Never mind. It was a problem on my end.

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 a pull request may close this issue.

6 participants