False positives in rspec change blocks

[Goltergaul]

rubocop-sequel thinks that rspec change expectations are database migrations:

e.g:

spec/app/repositories/run_session/strategy/mongo_db/hard_delete_spec.rb:67:41: C: Sequel/IrreversibleMigration: Avoid using document_count inside a change block. Use up & down blocks instead.
    it { expect { subject }.to change { document_count(user_id) }.by(-1) }

spec/app/repositories/sport_activity/wrappers/plausibility_spec.rb:225:60: C: Sequel/IrreversibleMigration: Avoid using find inside a change block. Use up & down blocks instead.
        expect { subject }.not_to(change { described_class.find(id: sport_activity.id).plausible })

[Goltergaul]

https://github.com/rubocop/rubocop-sequel/blob/master/lib/rubocop/cop/sequel/irreversible_migration.rb#L33 this should probably check further that the block is actually part of a sequel migration

[cyberdelia]

You may also configure rubocop to only run sequel cops on migrations related code, it will also speed up your checks overall.

[Goltergaul]

I know but I don't really want to need to add custom config for such things. Should ideally just work out of the box

[AlasdairWallaceMackie]

I'll work on a fix for this, sorry about that!

[Goltergaul]

no problem at all, just wanted to bring it to your attention :) Thanks for looking into it!

[cyberdelia]

I believe this was fixed in 0.3.6.

[Goltergaul]

Thank you @cyberdelia