Skip to content

Fix broken link in new expectation syntax blog post #160

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

Merged
merged 1 commit into from
Nov 18, 2020
Merged

Fix broken link in new expectation syntax blog post #160

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion source/blog/2012-06-15-rspecs-new-expectation-syntax.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ users plenty of time to get acquianted with it.

Let us know what you think!

[^foot_1]: As [Mislav reports](http://mislav.uniqpath.com/2011/06/ruby-verbose-mode/), when warnings are turned on, you can get a "Useless use of == in void context" warning.
[^foot_1]: As [Mislav reports](https://mislav.net/2011/06/ruby-verbose-mode/), when warnings are turned on, you can get a "Useless use of == in void context" warning.

[^foot_2]: On ruby 1.8, `x.should != y` is syntactic sugar for `!(x.should == y)` and RSpec has no way to distinguish `should ==` from `should !=`. On 1.9, we can distinguish between them (since `!=` can now be defined as a separate method), but it would be confusing to support it on 1.9 but not on 1.8, so we [decided to just raise an error instead](https://github.com/rspec/rspec-expectations/issues/33).

Expand Down