uninitialized constant when using module in custom initializer

Question

I'm working on a Rails (3.2) app and I need to execute some tasks when the app boots.

Since I want to keep the logic in a separate file I have also create lib/helinium.rb that looks like (with dummy run method)

class Helinium
  def self.run
    puts "running ...."
  end
end

And I have created a simple initializer file config/initializers/perform_checks.rb

Helinium.run

And everything seems fine. Now I wish to put the Helinium class within a module so the two files look respectively like

module Elemens
  class Helinium
      def self.run
        puts "running ...."
      end
  end
end

and

Elemens::Helinium.run

but when I try to boot the app I get

uninitialized constant Elemens (NameError)

Am I missing something here? Why the module is not found?

Thanks and have a nice day.

Community · Accepted Answer · 2017-05-23 12:25:02Z

10

explanation

This has something to do how the autoloading works in Rails.

Rails doesn't automatically require everything under /lib. It only auto loads when you try to use a new class name that matches a file name in lib.

You may check this post for more info:
https://stackoverflow.com/a/9819938/1188913

fix

To fix your issue you could

require 'lib/helinium'

OR

put the class into a folder called lib\elemens

edited May 23, 2017 at 12:25

CommunityBot

11 silver badge

answered Mar 15, 2013 at 7:28

deepflame

9281 gold badge8 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Sig Over a year ago

Thanks I though adding the following line to application.rb would be enough but actually it wasn't. config.autoload_paths += %W(#{config.root}/lib)

deepflame Over a year ago

it really depends on how you name the class inside and where you place it. You can also put the class into an 'elemens' folder to make it work.

Sig Over a year ago

So if I have lib/elemens/helinium.rb I don't need to require the file. Thanks for your reply

Sig Over a year ago

Sorry If I bother you again but is there a way to ensure my initializer is executed as last operation during the boot? I need to know the available models. I call ActiveRecord::Base.descendants but it returns an empty array. Thanks again.

deepflame Over a year ago

no worries, maybe this is something for a new question? Feel free to accept the answer if it solved your problem

Collectives™ on Stack Overflow

uninitialized constant when using module in custom initializer

1 Answer 1

explanation

fix

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

explanation

fix

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related