Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Cache] Remove TaggableCacheInterface, alias cache.app.taggable to CacheInterface #27398

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 31, 2018

Conversation

nicolas-grekas
Copy link
Member

@nicolas-grekas nicolas-grekas commented May 28, 2018

Q A
Branch? master
Bug fix? no
New feature? yes
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets -
License MIT
Doc PR -

Actually, there is no downside in using a taggable cache pool as a backend for CacheInterface.
This means we can simplify things and remove the TaggableCacheInterface and keep only CacheInterface (master-only).

@nicolas-grekas nicolas-grekas changed the title [Cache] Remove TaggableCacheInterface, make cache.app taggable [Cache] Remove TaggableCacheInterface, alias cache.app.taggable to CacheInterface May 28, 2018
@nicolas-grekas nicolas-grekas force-pushed the cache-always-taggable branch from 9a74cc6 to c250fbd Compare May 28, 2018 19:56
@fabpot
Copy link
Member

fabpot commented May 31, 2018

Thank you @nicolas-grekas.

@fabpot fabpot merged commit c250fbd into symfony:master May 31, 2018
fabpot added a commit that referenced this pull request May 31, 2018
….taggable to CacheInterface (nicolas-grekas)

This PR was merged into the 4.2-dev branch.

Discussion
----------

[Cache] Remove TaggableCacheInterface, alias cache.app.taggable to CacheInterface

| Q             | A
| ------------- | ---
| Branch?       | master
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | -
| License       | MIT
| Doc PR        | -

Actually, there is no downside in using a taggable cache pool as a backend for CacheInterface.
This means we can simplify things and remove the TaggableCacheInterface and keep only CacheInterface (master-only).

Commits
-------

c250fbd [Cache] Remove TaggableCacheInterface, alias cache.app.taggable to CacheInterface
@nicolas-grekas nicolas-grekas deleted the cache-always-taggable branch May 31, 2018 18:36
@nicolas-grekas nicolas-grekas modified the milestones: next, 4.2 Nov 1, 2018
This was referenced Nov 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants