Hacker News new | ask | show | jobs
by solnic 1303 days ago
You missed the context of this example - it's just there to show that IF you don't want to use constructor DI, you can put things in lib and they won't become part of the automatic DI system
1 comments

The point here, is, let's code in production.

No good production code allows such things to accidentially happen, so to me, it's the error from framework. What's the point of using a framework if it couldn't help me do silly things then ?

How would Hanami prevent this without messing with ruby constant lookup? Probably monkey patches to Kernel would be required.