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.

Sign up for GitHub

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

Jump to bottom

Deprecation warning with Rspec 3 #70

Closed
freemanoid opened this issue Jun 23, 2014 · 6 comments
Closed

Deprecation warning with Rspec 3 #70

freemanoid opened this issue Jun 23, 2014 · 6 comments
Labels
outdated Inactive - Outdated

Comments

@freemanoid
Copy link

I'm using rspec 3.0.0 and get the message when run rspec with Fuubar formatter.

Deprecation Warnings:

The Fuubar formatter uses the deprecated formatter interface not supported directly by RSpec 3. To continue to use this formatter you must install the rspec-legacy_formatters gem, which provides support for legacy formatters or upgrade the formatter to a compatible version. Formatter added at: /Users/user/.rvm/gems/ruby-1.9.3-p547/gems/zeus-0.15.1/lib/zeus/rails.rb:202:in `test'

If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
config.raise_errors_for_deprecations!, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

I guess it should be fixed instead of using legacy formatters?
@akerl
Copy link

akerl commented Jun 23, 2014

This warning doesn't appear in fuubar 2.0.0.rc1, so it looks like it's already known and fixed, there just hasn't been a fuubar release since rspec released version 3

@freemanoid
Copy link
Author

@akerl Nice, thanks!

@akerl
Copy link

akerl commented Jun 23, 2014

@jfelchner Is a new release in the pipeline to address this? I'm using the release candidate now, but would feel better tracking stable again

@jfelchner
Copy link
Collaborator

@akerl as soon as someone figures out #69 I'll push out 2.0.0 proper.

@plukevdh
Copy link
Contributor

plukevdh commented Aug 6, 2014

@jfelchner done. See #72

jfelchner pushed a commit that referenced this issue Aug 7, 2014
@plukevdh @jfelchner
Bugfix: Fix duplicate constant warnings
3fee745 
From the RC to the final release, RSpec changed their base formatter so that it
would include `rspec/core/formatters/console_codes`.  Due to this, and because
we were requiring it in fuubar as well, users were getting warning about the
fact that constants had already been defined.

Now we're just requiring `rspec/core/formatters/base_text_formatter` and
allowing it to require `console_codes` for us.

Issue URLs:
  * #69
  * #70
  * #72

Actions:
  References #69
  References #70
  References #72

--------------------------------------------------------------------------------
jfelchner pushed a commit that referenced this issue Apr 24, 2016
@plukevdh @jfelchner
Bugfix: Fix duplicate constant warnings
5af8a33 
From the RC to the final release, RSpec changed their base formatter so that it
would include `rspec/core/formatters/console_codes`.  Due to this, and because
we were requiring it in fuubar as well, users were getting warning about the
fact that constants had already been defined.

Now we're just requiring `rspec/core/formatters/base_text_formatter` and
allowing it to require `console_codes` for us.

Issue URLs:
  * #69
  * #70
  * #72

Actions:
  References #69
  References #70
  References #72

--------------------------------------------------------------------------------
@github-actions
Copy link

This issue has been closed automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot added the outdated Inactive - Outdated label Dec 28, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
outdated Inactive - Outdated
Milestone
No milestone
Development

No branches or pull requests
4 participants
@plukevdh @freemanoid @jfelchner @akerl