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
Since the current Zeitwerk integration does not reload engines if loaded as gems, Devise controllers do not get refreshed, and therefore after a reload their parent remains to be the (stale) class object stored in the original constant.
Issue reported by @cj, moved from fxn/zeitwerk#21.
This issue is in reference to fxn/zeitwerk#19 (comment).
Adding code to a controller once the server has loaded does not get executed/updated.
Steps to reproduce:
after_action { pp 'foo' }
toapp/controllers/application_controller.rb
Expected outcome:
foo
to the consoleCurrent work around:
config.autoloader = :classic
toconfig/application.rb
Screencast demonstrating issue:
https://cl.ly/577db63e745a
@fxn here is the Zeitwerk trace https://gist.github.com/cj/ffc8b578412034cebdd410bf534e4ab0
The text was updated successfully, but these errors were encountered: