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, the validator supports caching of the validator metadata using an internal CacheInterface and the currently only implementation ApcCache. I propose to deprecate this interface and class and use Doctrine\Common\Cache\Cache implementations instead, which has many more implementations available.
The text was updated successfully, but these errors were encountered:
This PR was merged into the 2.5-dev branch.
Discussion
----------
[Validator] Added Doctrine cache
| Q | A
| ------------- | ---
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | yes
| Tests pass? | yes
| Fixed tickets | #9887
| License | MIT
| Doc PR |
I propose to keep the `CacheInterface` and deprecate only the `ApcCache`.
It will leave the classes depending on a `CacheInterface` unchanged and will allow to adapt new cache providers in the future.
Commits
-------
3c4de45 [Validator] Added Doctrine cache
@bschussek When deprecating CacheInterface, how do you suggest to handle ValidatorBuilderInterface::setMetadataCache(CacheInterface $cache). Replace it with the doctrine cache interface? This would be a bc break and somewhat make doctrine/cache a required dependency.
Currently, the validator supports caching of the validator metadata using an internal
CacheInterface
and the currently only implementationApcCache
. I propose to deprecate this interface and class and useDoctrine\Common\Cache\Cache
implementations instead, which has many more implementations available.The text was updated successfully, but these errors were encountered: