Trouble with Zeitwerk reloading

[david (David Taylor)]

Have you seen this topic? If you follow the structure there (and in the plugin-skeleton), things should work pretty smoothly:

Structuring a plugin for Rails autoloading

Many plugins include lots of class definitions inside plugin.rb, or use require_relative to load ruby files. That works, but it comes with some disadvantages: No auto-reloading of changes in development. Any changes require a full server restart Getting the require calls in the right order can be painful If they are require’d outside the after_initialize block, then other autoloaded classes/modules may not be available There is a solution! Plugins can lean on the standard Rails autol…

An important part of Zeitwerk autoloading is the file names/paths, so it’s hard to identify the problem from the snippet you shared. Is that in a plugin.rb file? Or some other file?