Skip to content
loading...

re: The Importance of Knowing Your Gems VIEW POST

TOP OF THREAD FULL DISCUSSION
re: We have, probably more than I care to admit. Luckily, most of the monkey patches are not permanent. Usually we will monkey patch a gem in our cod...
 

more than I care to admit.

I tried to ask the question in the most neutral way in terms of judgment knowing there's bound to be some rationalization abound.

I think it's a tool at the disposal of Rubyists that gets fairly polarized, but everybody does it at some point for practical reasons.

Do you know of any static code analyzers that can detect all monkeypatches against vendor gems in a codebase?

find config/initializers -type f -name '*active*'

:-) :troll:

I do not know of any off the top of my head and a quick Google search didn't turn up much. Given handy Ruby methods like source_location I would bet it would not be hard to create one.

code of conduct - report abuse