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
Currently all individual caches are services in a separate Pimple container, which is set as the caches service of the application.
This makes it easy to pass the complete collection of defined caches to something, but at the same time makes it a bit more work to define or extend just a single cache at a time, because you have to extend the caches service first.
The question is: Is anyone using the caches service and would it be acceptable to remove this service and to setup caches as services of the application's container (e.g. cache.default)?
This change would also bring it more in line with other service providers, which create services on the application's container, e.g. Doctrine.
The text was updated successfully, but these errors were encountered:
Currently all individual caches are services in a separate Pimple container, which is set as the
caches
service of the application.This makes it easy to pass the complete collection of defined caches to something, but at the same time makes it a bit more work to define or extend just a single cache at a time, because you have to extend the
caches
service first.The question is: Is anyone using the
caches
service and would it be acceptable to remove this service and to setup caches as services of the application's container (e.g.cache.default
)?This change would also bring it more in line with other service providers, which create services on the application's container, e.g. Doctrine.
The text was updated successfully, but these errors were encountered: