-
-
Notifications
You must be signed in to change notification settings - Fork 763
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
Use warnings from rspec-support #1115
Conversation
@@ -1,7 +1,7 @@ | |||
$LOAD_PATH.unshift(File.expand_path("../../lib", __FILE__)) | |||
|
|||
require 'benchmark' | |||
require 'rspec/caller_filter' | |||
require 'rspec/support/caller_filter' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this benchmark should be moved to rspec-support.
I have some concerns about moving the bits that depend on rspec-core APIs (e.g. the deprecation formatter) into rspec-support: |
See rspec/rspec-support#7 for discussion on that... |
@@ -25,6 +25,12 @@ Gem::Specification.new do |s| | |||
|
|||
s.required_ruby_version = '>= 1.8.7' | |||
|
|||
if RSpec::Core::Version::STRING =~ /[a-zA-Z]+/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needs a comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added
Updated in light of rspec/rspec-support#7 |
Anyone had a chance to review? /cc @myronmarston @xaviershay |
LGTM! |
Use warnings from rspec-support
Switch over warnings and caller filter to rspec-support