You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
With the given set of dependencies properly installed via composer, I get a mismatch on the Sonata\Cache\CacheAdapterInterface interface - which does not belong to this project, but the dependencies resolution allowed it to be installed along, which I believe should be fixed upon this bug report.
Steps to reproduce
Installing a Symfony 3.4 application and requesting all the packages listed above, ended up with a mismatch on the sonata/cache package version that added a BC by changing such interface.
Expected results
Should either install a locked/earlier version, or just conflict and say that it cannot install due to conflicting versions.
Actual results
$ php bin/console debug:container -vvv
PHP Fatal error: Declaration of Symfony\Cmf\Bundle\BlockBundle\Cache\BlockJsCache::get(array $keys) must be compatible with Sonata\Cache\CacheAdapterInterface::get(array $keys
): Sonata\Cache\CacheElementInterface in /var/www/sms_new_site/current/vendor/symfony-cmf/block-bundle/src/Cache/BlockJsCache.php on line 26
In BlockJsCache.php line 26:
[Symfony\Component\Debug\Exception\FatalErrorException]
Compile Error: Declaration of Symfony\Cmf\Bundle\BlockBundle\Cache\BlockJsCache::get(array $keys) must be compatible with Sonata\Cache\CacheAdapterInterface::get(array $ke
ys): Sonata\Cache\CacheElementInterface
The text was updated successfully, but these errors were encountered:
could you do a pull request to add a conflicts section for cache >2.99 that we can put into 2.1? and if you have the time, prepare a pull request to upgrade the cacheintegration to sonata 3?
Yes that is is an issue. But the issue was in one our two minor versions of sonata-project/block-bundle, where they introduced BC breaks instead of the deprecation notices. If you want to get a really save sonata version you should use block-bundle from ^3.15.0, cause there also a strictness fix is included.
So how to solve:
either move the broken versions (3.12 and 3.13 from my POV) to your own conflicts or we should do it on block-bundle and release a patch. I also prepare a new minor version, where I dropped all smaler block-bundle-versions: #298
And the caching thing is an other issue. There i would recommend to move "sonata-project/cache": "<1.1.1" into conflicts and require "sonata-project/cache-bundle": "2.4.*". The 3.x versions there are not compatible atm. The got the BC-Breaks you currently see.
A thought though: should the block-bundle error out and not install, due to the known mismatched versions? By changing the conflict section as suggested by David a while back like:
Environment
Upgrading a CMF application from Symfony 2.8 top 3.4.
Sonata packages
Symfony packages
PHP version
Subject
With the given set of dependencies properly installed via composer, I get a mismatch on the
Sonata\Cache\CacheAdapterInterface
interface - which does not belong to this project, but the dependencies resolution allowed it to be installed along, which I believe should be fixed upon this bug report.Steps to reproduce
Installing a Symfony 3.4 application and requesting all the packages listed above, ended up with a mismatch on the
sonata/cache
package version that added a BC by changing such interface.Expected results
Should either install a locked/earlier version, or just conflict and say that it cannot install due to conflicting versions.
Actual results
The text was updated successfully, but these errors were encountered: