Phil Pirozhkov

> silently automatically adding the comma into the token just causes pain The guideline non-ambiguously tells to "strings without ... special characters in them", where a comma is a special...

Are you confident enough to state that a certain practice is poor, basing on just your personal experience? If you look at this `real-world-` meta-repos, you would notice that not...

@JohnCoates something like: 1. Clone it with sub modules (might require fixing refs as there are dead ones, and ones with renamed integration branches) 2. Write a cop that would...

> easily lead to errors with commas I believe there is or should be a cop that would catch punctuation inside percent literals, as they certainly are unintentional in most...

Now when I look at this guideline, I’d write the good example as something like ```ruby expect(article.errors).to have_key(:title) ``` Or would outright recommend using shoulda-matchers.

It will fail both ways, won’t it? I guess to save on cascade class autoloading.

We’re planning on extracting some cops into a new ‘rubocop-rspec-rails’ extension, but I still think that Minitest users would benefit from having this cop in ‘rubocop-rails’.

I support the idea of making a cop as unsafe for autocorrection. There's an [open issue in `rubocop` about dynamic safety](https://github.com/rubocop/rubocop/issues/11092). It would be nice if we could tell if...

@koic What's your take on having this cop in this repo?

I'm completely fine with making the cop `SafeAutocorrect: false`, but I'm usually very opposed to making it `Safe: false` as this effectively makes the cop disabled for everyone unless they...