Question

Why given a module like this:

module TestModule
  module Configuration
    # Return the configuration values set in this module
    def options
      puts "OPTIONS IS IN"
      puts self.inspect
    end
  end
end

I get that the options method is in TestModule and not in Configuration?

EDIT: I add the gem that I am taking a look at, and the one that has given me this confusion:

Check this file: configuration.rb in line 37 the method options is defined.

In the class Client however, when options is called (line 11) is used doing Awesome instead of Configuration. Why is that? I don’t see any class named Awesome where those modules are being mixed.

Answer 1

The gem in question does (in awesome.rb)

module Awesome
  extend Configuration
end

So all of the methods on Awesome::Configuration (such as options) become singleton methods on the Awesome module