Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zeitwerk::NameError #193

Closed
karthickattabomman opened this issue Aug 2, 2020 · 1 comment
Closed

Zeitwerk::NameError #193

karthickattabomman opened this issue Aug 2, 2020 · 1 comment

Comments

@karthickattabomman
Copy link

(expected file /home/maddy/Sites/DeviceMailer/app/controllers/registrations_controller.rb to define constant RegistrationsController, but didn't):

@jarednorman
Copy link
Member

Unfortunately, you've provided almost no context around this error, but if I had to guess I'd assume you've just set up a new Solidus app on Rails 6 (using the Zeitwerk autoloader) and wanted to make modifications to the registrations controlle and that the file referenced contains those modifications. If that's correct, then you should consider using a decorator to make the modifications and may also want to review the docs on project file structure and Zeitwerk as the error you've encountered is directly related to that.

It's not clear from the details you provided (which don't reference any files from this extension) that you've encountered a bug in the extension itself. If this is more of a support request, please instead us the #support channel on the Solidus Slack. Whether you follow up here or in Slack, more context would be very helpful:

  • What version of Ruby, Rails, Solidus, and solidus_auth_devise are you using?
  • What were you trying to do when you experienced this error?
  • What have you done to try to resolve this error?
  • What's in the file app/controllers/registrations_controller.rb? That's a file in your app, not in this extension, so it's not clear what's going on.

I'm closing this issue due to lack of details and because there's no evidence this is a bug in this extension. Please feel free to follow up with more information (so we can reopen the issue if it really is a bug) or take the issue to our #support channel. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants