Module: Kernel

Defined in:
lib/zeitwerk/kernel.rb

Class Method Summary collapse

Class Method Details

.require(path) ⇒ Object 



24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
 
# File 'lib/zeitwerk/kernel.rb', line 24

def require(path)
  if loader = Zeitwerk::Registry.loader_for(path)
    if path.end_with?(".rb")
      zeitwerk_original_require(path).tap do |required|
        loader.on_file_autoloaded(path) if required
      end
    else
      loader.on_dir_autoloaded(path)
      true
    end
  else
    zeitwerk_original_require(path).tap do |required|
      if required
        abspath = $LOADED_FEATURES.last
        if loader = Zeitwerk::Registry.loader_for(abspath)
          loader.on_file_autoloaded(abspath)
        end
      end
    end
  end
end

.zeitwerk_original_require ⇒ Object

We are going to decorate Kernel#require with two goals.

First, by intercepting Kernel#require calls, we are able to autovivify modules on required directories, and also do internal housekeeping when managed files are loaded.

On the other hand, if you publish a new version of a gem that is now managed by Zeitwerk, client code can reference directly your classes and modules and should not require anything. But if someone has legacy require calls around, they will work as expected, and in a compatible way. This feature is by now EXPERIMENTAL and UNDOCUMENTED.

We cannot decorate with prepend + super because Kernel has already been included in Object, and changes in ancestors don’t get propagated into already existing ancestor chains.



21
 
# File 'lib/zeitwerk/kernel.rb', line 21

alias_method :zeitwerk_original_require, :require