Remove Deprecated Code#12
Merged
albertosaurus merged 1 commit intoalbertosaurus:masterfrom Apr 8, 2016
Merged
Conversation
When running code in a test suite, it would throw the following warning
messages:
Deprecation Warnings:
`failure_message_for_should_not` is deprecated. Use
`failure_message_when_negated` instead. Called from
lib/testing/rspec.rb:98:in `block in <top (required)>'.
`failure_message_for_should` is deprecated. Use
`failure_message` instead. Called from
lib/testing/rspec.rb:90:in `block in <top (required)>'.
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.
2 deprecation warnings total
This change adopts the newer, generic DSL for writing RSpec matchers.
Contributor
Author
Owner
|
@kmwhite You have a newer version of rails than my dev version, I think. What would be the minimum version of RSpec where this would work? |
Contributor
Author
|
@albertosaurus Apologies for the delays -- work had me all over the place. It looks like |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running code in a test suite, it would throw the following warning
messages:
This change adopts the newer, generic DSL for writing RSpec matchers.
When testing these changes, they came back all green, but the file
spec/dummy/db/schema.rbhad been changed. Reviewing those changes, it showed that all theforce: truesettings in the table declarations had been changed toforce: :cascade. I did not include that file in this PR as I'm unsure if the source of it was a specific thing in Rails or my setup. I'm more happy to include that diff if desired.