Phil Pirozhkov
Phil Pirozhkov
> Actually, `be` accepting a block would be a nice matcher ;) There's [`satisfy`](https://relishapp.com/rspec/rspec-expectations/v/3-9/docs/built-in-matchers/satisfy-matcher) that does exactly that.
There are cases when this will result in false positives: ``` def expect_processed_value expect(process(value)) end def surprise_the_crowd eq(100) end it 'is hard to detect an expectation here' do expect_processed_value.to surprise_the_crowd...
`:example`/`:context` are two that [are recommended](https://github.com/rubocop-hq/rspec-style-guide#redundant-beforeeach). There is no strong recommendation *not* to use `:example` as a hook scope. Are you up to update the cop to provide this flexibility?
This sounds right.
Interesting! The same line of code triggers two cops. Both cops auto-correct, but one the same code one after moves the offensive line to "after the first let", and another...
> RuboCop's policy for `:crossing_deletions` (which is worse imo) is to `:accept` Can't say anything about that. I can imagine two cops, one operating on the statement and its first...
> [ ] Code documentation Looks pretty good already. > [ ] Add tests specifically for the extracted module We don't have much tests for modules, we rely on cops'...
Did that spec fail, @Darhazer ?
I remember we decided to `split` as opposed to using `start_with?` due to "whenever" that would also match the `/^when/` pattern. The logic of composition of `Prefixes` with `Suffixes` is...