Consider implementing autoload for Active Support

[jrmhaig]

#115 adds a fix to maintain compatibility with factory_bot_rails. As noted in the description of the PR there are other options that may be better, such as the autoload functionality in Active Support.

[tagliala]

Thanks. I can do the switch, but at the moment I do not know if it is worth.

Unfortunately I do not have the experience to understand the difference.

autoload is used, for example, in a gem which patches AR but does not have this issue with factory bot rails like Active Record Extended

Autoload PR: GeorgeKaraszi/ActiveRecordExtended#82

[jrmhaig]

No problem. If the current method works then I wouldn't worry about it too much. I'm currently having another look at sorting out the unit tests as I am not confident about making changes without understanding the effects.

[oskargargas]

After updating amoeba I see errors with initializers for:

• https://github.com/westonganger/active_snapshot
• https://github.com/collectiveidea/audited

Which all use ActiveSupport.on_load :active_record somewhere in code from what I checked.

It looks like wrapping initializers into ActiveSupport.on_load :active_record block works as a workaround. Thou I'll pin amoeba at 3.2 as less important element in my system.

Do you consider it as something that can be fixed with amoeba going autoload route? Or it's a bug that should also be submitted to Audited and ActiveSnapshot?

[tagliala]

Do you consider it as something that can be fixed with amoeba going autoload route?

Can't tell, not an expert of autoload mechanisms

I see errors with initializers

Can you please provide a reduced test case?

You can start with: https://github.com/diowa/ruby3-rails7-bootstrap-heroku