Lazy load interface definitions for generated factories about di HOT 9 CLOSED

@TomasVotruba https://github.com/lookyman/nette-auto-factory I need to stress that it has massive limitations (constructor arguments) and is basically just an exercise in using PhpGenerator.

from di.

The anonymous class solution would actually solve a problem I encountered just last week, where I tried to auto generate the interface itself. It works, but if you put it somewhere where the autoloading you already have doesn't see it, you are screwed. You have to either extend the PSR-4 autoload in composer.json, or register new path in RobotLoader in bootstrap. Neither of which you can do in runtime from an extension.

But, PHP 7 :/

Relevant https://github.com/lookyman/di/commit/6674d280d9f2911b63309903df20556315a2b2e2

from di.

👍

from di.

@lookyman How exactly in your case? And what was your issue? I didn't get that from referenced method.

from di.

@TomasVotruba

I had an extension, gave it some path, it scanned it for all classes of some type, generated a factory interface for each of them (and wrote it to some file in another path), and registered that interface as a service in container. But if that path with generated interfaces was not under autoload, the container couldn't be instantiated (though it could be built).

Kdyby/Doctrine, for example, runs into similar issue for generated entity proxies. But the proxies are loaded when the application is already running, so you have time to register an autoloader in Container::initialize(). In my case, you don't.

I have since abandoned that idea, but the commit I referenced could be used to solve this issue. Although I would much rather use the already existing afterCompile() for this and pass it a reference to all generated classes, but that would be a big BC break.

from di.

@lookyman Pretty neat usage :) thanks for explaining.

Do you have this extension somewhere on Github? Would love to see that.

from di.

@lookyman I was wondering... how far from your package is to create same service lazy loader (using proxy) that has Symfony?
https://symfony.com/doc/current/service_container/lazy_services.html

That would be awesome extension :)

from di.

The problem with autogenerated intefaces is that is then you use in the code interfaces that actually don't exist. It will break code completing in IDE or API documentation generators.

Proxies don't have these problems, but they have another.

from di.

@dg I know, as I've said, that whole extension was just an excercise. Not really that useful, except perhaps in very specific circumstances.

Anyway, I LOVE the anonymous class thingy you've made here. Thanks.

from di.