Phil Pirozhkov

I've discovered ~three~ two completely valid options for correction of: ```ruby expect([-1,2,3].all? { |x| x.positive? }).to be(true) ``` The difference is in the failure message. For the original: ``` Failure/Error:...

Thanks for the bump, @inkstak . Let me quickly rebase it.

@bquorning @Darhazer WDYT?

@bquorning I won't be merging this so far, not to interfere with the release.

Thank you, @kuahyeow ! Please accept our apologies it took two years to merge.

Adding a method to RuboCop for extensions to load ownself's config looks strange to me overall. Shouldn't RuboCop decide on its own which config to load depending on `require` in...

I might be mistaken, but it seems that this scheme circumvents the ability of extensions to require other extensions without explicitly `require`'ing them from Ruby code. When extension's `config/default.yml` gets...

Do you use this metadata in some way, or is it there for purely informational purpose? An option to trick the cop would be to: ```ruby describe SomeService, 'live', :live...

I'm puzzled to find a better option off the top of my head. On the other head I'm not certain if this is a widespread naming scheme, and in this...

Frankly, I find it puzzling why the following passes: ```ruby expect_no_offenses(