@timriley ok, now I remember why I did that. The interactors are copied as-they-are from my legacy project, allowing me to smoothly prepare my migration (v2), while still modifying things in production (v1.3). So the interactor classes don’t have the expected path for auto loading, unless I tweak each one of them a bit, which I don’t want to do right now.
So my “provider” (which is not a real one, I agree) is a sort of poor man’s autoloading, allowing to bootstrap my legacy code into the new one.
Leveraging the true power of the container will be one of the first projects, after I migrated (I have 4 projects to migrate, of of them being really huge, so it could take time)