Updating Zeitwerk to `2.5.0.beta2` breaks loading of resources about madmin

[excid3]

This took some serious time to figure out but I got it working. 🔥

[arschrier]

Spoke too soon! Thought this was related to Zeitwerk itself, but it appears this has to do with the way Rails now auto loads paths.

This is the breaking commit from Rails: rails/rails@2306a8e.

I am not an expert here, but is Rails eager loading the directory before engines are initialized?

[mattpolito]

@excid3 of course... trying to figure it out myself :-)

[excid3]

I had to dig through the Rails source code to figure it out. Couldn't find any examples or anything. The previous stuff was what I had found in a blog post, but this works consistently across all Rails versions using before_configuration. I didn't even know that was a callback you could use until I started reading the Rails source. 😅

[arschrier]

Telling Rails to collapse the resources directory fixed the issue. I did so by adding the following to config/application.rb:

Rails.autoloaders.main.collapse('app/madmin/resources')

[excid3]

Is this something that changed specifically in Zeitwerk 2.5?

[excid3]

Could be that the Madmin initializer isn't running early enough now. We do a similar thing to make sure the autoload paths are added before they get frozen.

https://github.com/excid3/madmin/blob/master/lib/madmin/engine.rb#L3

[mattpolito]

Can confirm... resource loading does not appear to work in Rails 7 alpha

[excid3]

PRs welcome if you figure out what's going on. 👍

[mattpolito]

@excid3 did you come across something that shows path loading needs to happen 'before configuration' or was that just the hook placement that ended up working?