Ruby (rails) conflicting class and modules names when nested

Question

I have a basic User model in app/models/user.rb. I also have a few services in lib. For example, I have lib/services/user/creation_service.rb. The following code generates an error:

# lib/services/user/creation_service.rb

module Services
  module User
    class CreationService
      ...
      def create_new_user
        # User.new below causes an error because it defaults to Services::User which is a module instead of User which is an ActiveRecord class
        User.new 
        ...
      end
      ...
    end
  end
end

Is there any way to get User.new to refer to app/models/user.rb instead of the Services::User module in the code above?

Any help would be greatly appreciated!

::User.new would do the trick

Konstantin Strukov
– Konstantin Strukov

2021-08-11 16:03:55 +00:00
Commented Aug 11, 2021 at 16:03 — Konstantin Strukov
– Konstantin Strukov, Commented Aug 11, 2021 at 16:03

Clark Taylor · Accepted Answer · 2021-08-11 16:04:06Z

1

Use ::User.new instead of User.new. The double colon basically tells ruby to look for the constant that does not have a parent.

So in this case ::User will point to User which is a class instead of Services::User which is a module.

answered Aug 11, 2021 at 16:04

Clark Taylor

4714 silver badges13 bronze badges

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

Collectives™ on Stack Overflow

Ruby (rails) conflicting class and modules names when nested

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related