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

Use is_expected.to instead of should #215

Closed
wants to merge 1 commit into from
Closed

Use is_expected.to instead of should #215

wants to merge 1 commit into from

Commits on Aug 6, 2014

  1. Use is_expected.to instead of should 

    Even though we've switched to the `expect` syntax, we've still been using
`should` for one-liners with an implicit subject. RSpec 3 introduced
`is_expected.to` as an alternative. Myron Marston explains:

> Some users have expressed confusion about how this should relates to the
> expect syntax and if you can continue using it. It will continue to be
> available in RSpec 3 (again, regardless of your syntax configuration), but
> we’ve also added an alternate API that is a bit more consistent with the
> expect syntax

From: [New API for
one-liners](http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new_api_for_oneliners_)
    @JoelQ
    JoelQ committed Aug 6, 2014
    Configuration menu
    Copy the full SHA
    cb60d74 View commit details
    Browse the repository at this point in the history