The change log describes what is "Added", "Removed", "Changed" or "Fixed" between each release.
Cache\Taggable\Exception\InvalidArgumentException
- We do not throw
Cache\Adapter\Common\Exception\InvalidArgumentException
anymore. Instead we throwCache\Taggable\Exception\InvalidArgumentException
. Both exceptions do implementPsr\Cache\InvalidArgumentException
- We do not require
cache/adapter-common
- Deprecated interfaces
TaggableItemInterface
andTaggablePoolInterface
- Bug on
TaggablePSR6ItemAdapter::isItemCreatedHere
where item value wasnull
.
- Support for
TaggableCacheItemPoolInterface
- The behavior of
TaggablePSR6ItemAdapter::getTags()
has changed. It will not return the tags stored in the cache storage.
TaggablePoolTrait
- Deprecated
TaggablePoolInterface
in favor ofCache\TagInterop\TaggableCacheItemPoolInterface
- Deprecated
TaggableItemInterface
in favor ofCache\TagInterop\TaggableCacheItemInterface
- Removed support for
TaggablePoolInterface
andTaggableItemInterface
TaggablePSR6ItemAdapter::getTags()
. UseTaggablePSR6ItemAdapter::getPreviousTags()
TaggablePSR6ItemAdapter::addTag()
. UseTaggablePSR6ItemAdapter::setTags()
- Do not lose the data when you start using the
TaggablePSR6PoolAdapter
- Updated version for integration tests
- Made
TaggablePSR6PoolAdapter::getTags
protected instead of private
- Saving an expired value should be the same as removing that value
This is a big BC break. The API is rewritten and how we store tags has changed. Each tag is a key to a list in the cache storage. The list contains keys to items that uses that tag.
- The
TaggableItemInterface
is completely rewritten. It extendsCacheItemInterface
and has three methods:getTags
,setTags
andaddTag
. - The
TaggablePoolInterface
is also rewritten. It has a newclearTags
function. - The
TaggablePoolTrait
has new methods to manipulate the list of tags.
No changelog before this version