bug symfony#31418 [FrameworkBundle] clarify the possible class/interface of the cache (xabbuh)

nicolas-grekas · nicolas-grekas · commit 81b415767ed4 · 2019-05-09T10:32:22.000+02:00
This PR was merged into the 3.4 branch. Discussion ---------- [FrameworkBundle] clarify the possible class/interface of the cache | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | | License | MIT | Doc PR | When the fallback cache pool is returned (on PHP 5.6, HHVM, or when Opcache is disabled), the configured service can be any implementation of the CacheItemPoolInterface. Commits ------- 4027374 clarify the possible class/interface of the cache
diff --git a/src/Symfony/Bundle/FrameworkBundle/Resources/config/serializer.xml b/src/Symfony/Bundle/FrameworkBundle/Resources/config/serializer.xml
@@ -82,7 +82,7 @@
             <tag name="kernel.cache_warmer" />
         </service>
 
-        <service id="serializer.mapping.cache.symfony" class="Symfony\Component\Cache\Adapter\PhpArrayAdapter">
+        <service id="serializer.mapping.cache.symfony" class="Psr\Cache\CacheItemPoolInterface">
             <factory class="Symfony\Component\Cache\Adapter\PhpArrayAdapter" method="create" />
             <argument>%serializer.mapping.cache.file%</argument>
             <argument type="service" id="cache.serializer" />
