Closed
Description
Using this bundle (v1.6.0) with Symfony 4.3 will have Composer generate a couple of "Warning: Ambiguous class resolution" when trying to generate an optimized autoloader.
$ composer dump-autoload --optimize
Generating optimized autoload files
Warning: Ambiguous class resolution, "Symfony\Contracts\Cache\CallbackInterface" was found in both "/var/www/vendor/symfony/cache-contracts/CallbackInterface.php" and "/var/www/vendor/symfony/contracts/Cache/CallbackInterface.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Contracts\Cache\ItemInterface" was found in both "/var/www/vendor/symfony/cache-contracts/ItemInterface.php" and "/var/www/vendor/symfony/contracts/Cache/ItemInterface.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Contracts\Cache\CacheInterface" was found in both "/var/www/vendor/symfony/cache-contracts/CacheInterface.php" and "/var/www/vendor/symfony/contracts/Cache/CacheInterface.php", the first will be used.
(snip)
The framework will load some traits and interfaces from /symfony/service-contracts/ while /webpack-encore-bundle/ will try to load the same from /symfony/contracts/
$ composer why symfony/contracts
symfony/webpack-encore-bundle v1.6.0 requires symfony/contracts (^1.0)
$ composer why symfony/service-contracts
symfony/cache v4.3.0 requires symfony/service-contracts (^1.1)
symfony/console v4.3.0 requires symfony/service-contracts (^1.1)
symfony/dependency-injection v4.3.0 requires symfony/service-contracts (^1.1.2)
symfony/doctrine-bridge v4.3.0 requires symfony/service-contracts (^1.1)
symfony/expression-language v4.3.0 requires symfony/service-contracts (^1.1)
symfony/monolog-bridge v4.3.0 requires symfony/service-contracts (^1.1)
symfony/security-core v4.3.0 requires symfony/service-contracts (^1.1)
symfony/stopwatch v4.3.0 requires symfony/service-contracts (^1.0)
Could this bundle bump it's requirement to symfony/service-contracts too?
Metadata
Metadata
Assignees
Labels
No labels