Posted 3 months ago. Visible to the public. Repeats.

Rails: How to use prepend to avoid monkey patches in modules

Let's say you have a gem which has the following module:

Copy
module SuperClient

  def self.foo
    'Foo'
  end
  
  def bar
    'Bar'
  end

end

For reasons you need to override foo and bar.

Keep in mind: Your code quality is getting worse with with each prepend (other developers are not happy to find many library extensions). Try to avoid it if possible.

Add a lib/ext/super_client.rb to your project (Folder or file needs to be required in an initializer)
Add the extension, which overrides both methods (prepend is available since ruby >=2)

Copy
module SuperClientExtension

  def self.prepended(base)
    base.singleton_class.send(:prepend, ClassMethods)
  end

  module ClassMethods
    def foo
      'New foo'
    end
  end
  
  def bar
    'New bar'
  end
  
end

module SuperClient
  prepend SuperClientExtension
end

Test

Copy
class Test; include SuperClient; end

SuperClient.foo => 'New foo'
Test.new.bar => 'New bar'

Check out our new e-book:

Growing Rails Applications in Practice

Learn to structure large Ruby on Rails codebases with the tools you already know and love.

Learn more

Owner of this card:

Emanuel De

Rails: How to use prepend to avoid monkey patches in modules

Test

Owner of this card:

Your thanks were sent
to !

License for source code

Rails: How to use prepend to avoid monkey patches in modules

Test

Owner of this card:

Your thanks were sent to !

License for source code

Your thanks were sent
to !