-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Serializer doc issues #7282
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
Comments
Can anyone with experience using Serializer please verify this bug report? Thanks! |
The |
If someone understands the Serializer component well, please continue my failed pull request to fix this: https://github.com/symfony/symfony-docs/pull/8133/files Thanks! |
@xabbuh in my failed PR (#8133) you made some useful comments about how to fix this. Do you think you could finish this issue yourself? It's the last one pending in the ancient Symfony 3.1 milestone, so it'd be great to finish it. Thank you! |
see #10039 |
Reported by @magarzon in the #support channel of Symfony's Slack:
Is there a way to disable the cache for the serializer? I'm having problems with the cached metadata, I've tried to set cache: false in framework config, but it's not working
Weird thing is that there is a service defined serializer.mapping.cache.symfony that is a "memory cache", but that doesn't works with the serializer, it complains that doesn't implements Doctrine\Common\Cache\Cache interface. Probably an issue?
because it has the "same" name as the recommended cache in the documentation, serializer.mapping.cache.apc
Probably it's my code, I'm going to check
No, it's not my code, it's documentation not up-to-date and probably bad naming: serializer.mapping.cache.apc is deprecated since 3.1, but is still recommended in this doc without any warning: https://symfony.com/doc/current/serializer.html#enabling-the-metadata-cache
The text was updated successfully, but these errors were encountered: