-
Notifications
You must be signed in to change notification settings - Fork 208
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
Remove 1.8 references. #647
Conversation
|
||
if RUBY_VERSION > '1.8' | ||
# requires ruby 1.9+, on 1.8 we'll fall back to the old regex parsing | ||
gem 'rspec-json_expectations', '~> 1.4' |
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.
This block should always be present, rather than removed.
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.
You're correct. I missed that. Why did this not break during the unit tests?
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.
Because @binford2k was nice enough to politely skip that when the module doesn't load with a Rescue statement.
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.
Oh, maybe that should go away as well.
end | ||
|
||
group :development do | ||
# For Changelog generation | ||
if RUBY_VERSION > '1.9' |
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.
Does > 1.9
cover 1.9.3 or only 2.0.0+?
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 does cover 1.9.3. It was to prevent 1.8. I'll double check from build logs.
I'd like @binford2k to take a quick look and see if there's anywhere else the json_expectations would need adjustment. |
No description provided.