Permalink
Switch branches/tags
Commits on Dec 16, 2012
  1. 2.12.1 release.

    myronmarston committed Dec 16, 2012
Commits on Dec 7, 2012
  1. Merge pull request #194 from stevenharman/issue_188_custom_matchers_w…

    …ith_match
    
    Allow custom matchers to use built-in #match
    myronmarston committed Dec 7, 2012
Commits on Dec 6, 2012
  1. Allow custom matchers to use #match built in

    Addresses problem with dispatching the #match matcher from within a
    custom matcher. (Wow... what a mouthful) See Issue #188.
    stevenharman committed Dec 6, 2012
  2. Cleanup whitespace

    stevenharman committed Dec 6, 2012
  3. Merge pull request #193 from rspec/hash_match_array_failure

    Provide a clear failure message when using `{}.should =~ {}`.
    myronmarston committed Dec 6, 2012
  4. Provide a clear failure message when using `{}.should =~ {}`.

    The match_array matcher (delegated to by `=~` for enumerables) is
    not meant to be used for hashes, but the `should =~` syntax doesn't
    make that obvious. Previously, you would get a failure like:
    
         Failure/Error: actual.should =~ actual
           expected: {:foo=>"bar"}
                got: {:foo=>"bar"} (using =~)
    
    ...which is pretty confusing. Our `match_array` matcher already
    includes handling for invalid arguments (such as hashes) to return
    a clear failure message, but it wasn't being used for an expression
    like `{}.should =~ {}` because it was only registered as an operator
    matcher for `Array`. This changes it so that it is registered as an
    operator matcher for any Enumerable. This improves the failure message
    for enumerable types like hash and set, but on its own, it could cause
    breakage for things like 1.8 strings that are Enumerable but also
    define a reasonable `=~`.  The fix here changes the operator matcher
    delegation logic so that it only delegates to the registered matcher
    if the object has the generic Kernel implementation of the operator.
    If it has a more specific implementation, we assume the user actually
    wants to match using the given operator itself.
    
    Fixes #191.
    myronmarston committed Dec 6, 2012
Commits on Dec 5, 2012
  1. Merge pull request #192 from alindeman/operator_registry_considers_an…

    …cestors
    
    OperatorMatcher considers ancestor chain
    myronmarston committed Dec 5, 2012
Commits on Dec 4, 2012
  1. OperatorMatcher considers ancestor chain

    * Related #191
    alindeman committed Dec 4, 2012
Commits on Nov 13, 2012
  1. Fixes changes link

    alindeman committed Nov 13, 2012
  2. bump version to 2.12

    dchelimsky committed Nov 13, 2012
  3. Updates to rake 10

    alindeman committed Nov 13, 2012
  4. prep for 2.12 [ci-skip]

    dchelimsky committed Nov 13, 2012
Commits on Nov 9, 2012
  1. Merge pull request #187 from nanocity/yield_arguments

    Use 'empty?' instead of 'any?' and 'none?' to match 'nil' and 'false'
    alindeman committed Nov 9, 2012
  2. Use 'empty?' instead of 'any?' and 'none?' in order to match 'nil' an…

    …d 'false' as argument values
    nanocity committed Nov 9, 2012
Commits on Oct 27, 2012
  1. Update changelog.

    [ci skip]
    myronmarston committed Oct 27, 2012
  2. Merge pull request #184 from mortice/implicit-docstring-for-instance-…

    …of-matcher
    
    Fix generated docstring for BeAnInstanceOf when Class#inspect changed
    myronmarston committed Oct 27, 2012
  3. Make the error message more useful when using match_array

    * Now the error message will let you know if you're trying to match an
      array against something that isn't an array-like thing.
    * Closes #186
    * Fixes #185
    samphippen committed with alindeman Oct 26, 2012
Commits on Oct 26, 2012
Commits on Oct 23, 2012
  1. Cleanup whitespace.

    myronmarston committed Oct 23, 2012
Commits on Oct 21, 2012
Commits on Oct 17, 2012
  1. Update changelog.

    myronmarston committed Oct 17, 2012
  2. Cleanup whitespace.

    myronmarston committed Oct 17, 2012
Commits on Oct 16, 2012
  1. JRuby --1.9 is green

    alindeman committed Oct 16, 2012
  2. Build on JRuby --1.9

    alindeman committed Oct 16, 2012