Skip to content

update the serializer cache description #10039

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 11, 2018
Merged

update the serializer cache description #10039

merged 1 commit into from
Jul 11, 2018

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Jul 10, 2018

This fixes #7282.

@xabbuh xabbuh added this to the 3.4 milestone Jul 10, 2018
@xabbuh
Copy link
Member Author

xabbuh commented Jul 10, 2018

We could also talk about the cache.serializer service and that you could register an alias to let it point to a different cache pool. But IMO it's an absolute edge case to use a cache pool for the serializer that is different from the system cache pool and documenting it here would be more confusing than helping at all.

@xabbuh xabbuh mentioned this pull request Jul 10, 2018
Closed
@javiereguiluz
Copy link
Member

Thanks Christian! I love it when we remove lots of lines :)

@javiereguiluz javiereguiluz merged commit b65d15a into symfony:3.4 Jul 11, 2018
javiereguiluz added a commit that referenced this pull request Jul 11, 2018
@javiereguiluz
minor #10039 update the serializer cache description (xabbuh)
556329c 
This PR was merged into the 3.4 branch.

Discussion
----------

update the serializer cache description

This fixes #7282.

Commits
-------

b65d15a update the serializer cache description
@xabbuh xabbuh deleted the issue-7282 branch July 11, 2018 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Serializer Status: Reviewed
Projects
None yet
Milestone
3.4
Development

Successfully merging this pull request may close these issues.
3 participants
@xabbuh @javiereguiluz @carsonbot