{"push_id":941063626,"size":1,"distinct_size":1,"ref":"refs/heads/neg-match-parity","head":"0973737e076fbffb8ca7404daded3e77ee572278","before":"5d4d5c56a7d6f96305d077b8b85850c1ae5dcb3d","commits":[{"sha":"0973737e076fbffb8ca7404daded3e77ee572278","author":{"email":"711c73f64afdce07b7e38039a96d2224209e9a6c@chrisarcand.com","name":"chrisarcand"},"message":"Fix #handle_matcher for negative expectations\n\nIn quick summary, the negation here has allowed the following thing to be occur\nin RSpec for a very, very long time:\n\n```\n> expect(\"foo\").to eq \"foo\"\n=> true\nGood!\n\n> expect(\"foo\").to eq \"bar\"\nRSpec::Expectations::ExpectationNotMetError:\nexpected: \"bar\"\n     got: \"foo\"\n\n(compared using ==)\nGood!\n\n> expect(\"foo\").not_to eq \"foo\"\nRSpec::Expectations::ExpectationNotMetError:\nexpected: value != \"foo\"\n     got: \"foo\"\n\n(compared using ==)\nGood!\n\n> expect(\"foo\").not_to eq \"bar\"\n=> false\nWRONG. Should raise ExpectationNotMetError\n```\n\nThe negation has been around since the extraction of rspec-expectations, so\neither it was intended at some point in time to indicate a negative matcher\npassing (and this code was never corrected) or something funny must have\nhappened with the numerous refactorings that have occurred in this area over the\nyears.\n\nThe more prominent trail of commits in this area:\n\nhttps://github.com/rspec/rspec-expectations/commit/3ba4b82ed09ea4edf6691c1007635b3f81512bca\nhttps://github.com/rspec/rspec-expectations/commit/ef101659c1f8f78171e6311e9ae95107b7b5b36f\nhttps://github.com/rspec/rspec-expectations/commit/358ce674a479118cf486d58f8ee7efe2660c9075\n\nFun to find and fix!","distinct":true,"url":"https://api.github.com/repos/chrisarcand/rspec-expectations/commits/0973737e076fbffb8ca7404daded3e77ee572278"}]}