Rails console: Unable to autoload constant

Question

I have a Customer_ratings model that allows users to leave feedback on each other. The web app is working properly, and feedback is collected, stored and displayed.

I wanted to go in and delete some feedback through the rails console, but when I enter Customer_rating.all, I get the following error:

LoadError: Unable to autoload constant Customer_rating, expected /Users/myapps/app/models/customer_rating.rb to define it

Similarly, if I enter Customer_rating[0], I get:

RuntimeError: Circular dependency detected while autoloading constant Customer_rating

I don't have this issue while accessing other tables through my console.

What could be causing the issue, and why wouldn't this error prohibit Customer_ratings from working properly through the web app?

I see couple of problems here. Lets discuss this on chat http://chat.stackoverflow.com/rooms/48530/ror — Kirti Thorat, Mar 31 '14 at 23:12
FYI all constants need to be [CamelCase](http://en.wikipedia.org/wiki/CamelCase) -- you should be calling `CustomerRating` — Richard Peck, Apr 01 '14 at 15:42

Kirti Thorat · Accepted Answer · 2015-05-15T17:40:39.420

50

It seems like a case of messed up naming convention.

As per Rails naming convention, file names should be in snake_case and class names in CamelCase. In your scenario, the file name should be customer_rating.rb and class name should be CustomerRating.

After making these changes, use CustomerRating.all(as the updated class name is CustomerRating) to fetch all the customer ratings. Do not use Customer_rating.all.

edited May 15 '15 at 17:40

answered Apr 01 '14 at 15:49

Kirti Thorat

52,578
9
101
108

1

CustomerRating.all vs Cutomer_rating.all was the issue. Thanks! – dmt2989 Apr 01 '14 at 15:52
I got similar error message in different case. My mistake was, I made a Typo in class name and rails was unable to find the expected class in the file. Fixed now. – Sandesh Soni May 03 '16 at 16:57

score 7 · Answer 2 · answered Aug 23 '14 at 18:24

I'd also like to add a scenario of this problem that I found for future reference.

I'm running Rails 4.0 and I had this same problem but what happened was I had a model named Student inside student.rb that was contained in a folder called Student. I didn't realize it at first but the folder name was the problem. Changing the folder name to something other than a model name solved the problem.

jackhowa · Answer 3 · 2021-04-01T19:05:50.847

If the naming convention is not off, like in this question, it may be an issue on initial first load if you're making a lot of requests at the same time. I experienced this with nested controllers Api::LocationsController.

I solved it by enabled eager_load in development env:

Rails.application.configure do
  ...
  # Enabled this to avoid crash unable to autoload controller 
  # Error happens when you start and stop server on initial requests
  # solution found via https://github.com/rails/rails/issues/32082#issuecomment-367715194
  config.eager_load = true

I based this off of rails issues comments: https://github.com/rails/rails/issues/32082#issuecomment-367715194

score -4 · Answer 4 · edited Aug 17 '18 at 21:17

-4

You just need to modify the name of the Module

For example if the link is http://sairam.esy.es/users/customer_rating then you controller should like be

module Users
  class RatingController
    # ...

    def customer_rating
      # ...
    end

    # ...
  end
end

edited Aug 17 '18 at 21:17

Tim Krins

3,134
1
23
25

answered Aug 04 '17 at 14:21

Sai Ram Reddy

1,079
13
14

This is not Ruby syntax – Houen Feb 07 '18 at 07:12

Rails console: Unable to autoload constant

4 Answers4