Ignore UtilityFunction cop in all specs

[pyromaniackeca]

No description provided.

[pyromaniackeca]

/reviewme @rainforestapp/devs @grodowski

I also tried to see why the data_corrections aren't being excluded, but didn't have much luck, I'll probably try again in the future.

[grodowski]

@pyromaniackeca I found out today that reek has a bunch of issues open related to this: e.g. troessner/reek#1482.

Might have something to do with what file metadata pronto-reek passes to reek here.

[grodowski]

The other aspect of how pronto-reek calls Reek::Examiner with a file argument might be that in this case the exclude_paths are not used at all?troessner/reek@cd46040

I read up how Reek works under the hood and I'm pretty sure the above is true: SourceLocator, which does care about the excude_paths config is never used by pronto:

• we might want to configure excludes in pronto's config (I see you tried that in Rainforest in a commit I can't find now)
• we might contribute to pronto-reek (and how it uses the configuration object) to improve that (if you're looking for an OSS contrib opportunity, it's here)

[pyromaniackeca]

@grodowski Thanks for looking into it.

I think you're right that exclude_paths are completely ignored. In my attempts to make it work, I opened up the reek gem and set some breakpoints to try and figure out what's going on and I could not figure out where exactly it was checking the exclude_paths when run via pronto.

[pyromaniackeca]

We've stopped reporting reek issues in PRs entirely, so this is no longer required.