How does this gem differs from Rails strict_loading?

[aelkoussy]

Thanks for the great work on this gem.
Can we compare more in depth why would this gem be useful given that Rails strict_loading exists? (and maybe we can add it to the Readme)

For me, I understand that strict_loading prevents all kinds of lazy loading, which includes n+1 issues but also includes other things, it is very hard for me to pinpoint how those 2 cases diverge

In other words: what are lazy loading cases that will throw exception in strict_loading but are NOT N+1 issues?
Plus, any other points you think are handled better in Prosopite

Thanks

[technicalpickles]

If you are like me, and weren't familiar with strict_loading, it was added in Rails 6.1

• Add strict_loading mode to optionally prevent lazy loading rails/rails#37400
• Rails has added strict loading mode to prevent lazy loading | Saeloun Blog

[aelkoussy]

Thanks, I know about strict_loading and many resources cover it well, but I hope the author of the gem (or someone) can explain how Prosopite is different than Rails strict_loading and what are the benefits of using it instead.

[santib]

Interested in hearing more about the differences as well

[TafadzwaD]

@aelkoussy I came across this learningtapestry/lcms-engine#151 (comment) , hope it helps

[abuisman]

I just learned about strict_loading today. What do I gain from using prosopite vs strict_loading? You can enable strict_loading globally and every n+1 will be detected right? Or does prosopite do something else?