Use Expressive Skeleton installer with PHP-DI results in error? about zend-di-config HOT 10 CLOSED

@holtkamp thank you for the report.

I don't really use zend_view. However, zend-view involves zend-service-manager whose uses obsoleted interop-container.

Second, zend service acts as a container so I don't see the interest of using many containers in the same project.

I will close this issue as it is not related to this package we should wait zend service upgrade.

from zend-di-config.

@elie29 works perfectly! Very elegant approach, compliments 👍

from zend-di-config.

Thank you for your feedback.

I am using PHP-DI with zend framework and zend expressive with no issues. However, you may need container-interop as suggested by zend expressive if you want to use lazy or Abstract Factory.

I tried now the installation with composer serve and everything works correctly:

from zend-di-config.

@elie29 thanks for the swift response. Will try again coming week and report back here. Probably I did something wrong 😉

from zend-di-config.

It seems related to my preference to use zend-view as template engine:

Which template engine do you want to use?
  [1] Plates
  [2] Twig
  [3] zend-view installs zend-servicemanager
  [n] None of the above

This involves zend-servicemanager, which uses Interop\Container\ContainerInterface in Zend\ServiceManager\AbstractPluginManager::__construct(), at https://github.com/zendframework/zend-servicemanager/blob/release-2.7.11/src/AbstractPluginManager.php#L12

While the PHP-DI container implements Psr\Container\ContainerInterface, see https://github.com/PHP-DI/PHP-DI/blob/6.0.5/src/Container.php#L29

Workarounds:

• When using Twig as template engine everything works directly, since this does not involve the Zend ServiceManager
• When using Zend View as template engine, we should change DI\Container to implement Interop\Container\ContainerInterface instead of Psr\Container\ContainerInterface
  • this is not a very elegant option, since the preferred approach would be to use Psr\Container\ContainerInterface. This seems to be a "known" issue, see: zendframework/zend-servicemanager#184

Not sure whether a solution exists other then "waiting" zend-servicemanager v4...

from zend-di-config.

You need to decorate your PSR container for Interop container compatibility, see this comment

from zend-di-config.

No need for a decorator. Aliasing with Psr container is enough

from zend-di-config.

Until zend service manager release version 4, we have to wrap DI\Container by implementing Interop\Container\ContainerInterface

from zend-di-config.

@holtkamp I released a new version with the wrapper would you please test https://github.com/elie29/zend-di-config/releases/tag/v3.0.9

from zend-di-config.

@holtkamp thank you for testing the version. We can promote it now!

from zend-di-config.