You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see that by #554 it should no longer be required to add require "good_job/engine" line, but it does not work for me in development environment.
When visiting mounted "/good_job" path I'm getting: uninitialized constant GoodJob::JobsController Object.const_get(camel_cased_word)
It's the same error on 2.99 and 3.0 versions
Nuts! There shouldn't be any harm in adding back in require "good_job/engine".
I wish I knew how to diagnose why some Rails apps are able to implicitly autoload engines... and some aren't. The two commands I was using to debug that feature in #634 were:
bin/rails zeitwerk:check, which hopefully should output "All is good!"
bin/rails runner 'pp ActiveSupport::Dependencies.autoload_paths' which should include GoodJob's app/... files. e.g.
I think I should re-add the require 'good_job/engine' to the Readme as an optional suggestion. It shouldn't be required, but I bet you're not the only person experiencing problems.
I can see that by #554 it should no longer be required to add
require "good_job/engine"
line, but it does not work for me in development environment.When visiting mounted "/good_job" path I'm getting:
uninitialized constant GoodJob::JobsController Object.const_get(camel_cased_word)
It's the same error on 2.99 and 3.0 versions
The text was updated successfully, but these errors were encountered: