Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Serializer] Fix configuration of the cache key#36340
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
alanpoulain commentedApr 4, 2020
It's only an issue if the default context for the cache key is changed by a child class and if the constructor is called afterwards, doesn't it? |
src/Symfony/Component/Serializer/Normalizer/AbstractObjectNormalizer.php OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
nicolas-grekas commentedApr 4, 2020
A test case would be nice if you can. |
dunglas commentedApr 5, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@alanpoulain it's even the case if you just pass the keys to exclude as parameter of the constructor. |
fabpot commentedAug 11, 2020
Is this one still relevant? I see that the original issue has been closed as the problem has been fixed in PHP itself IIUC? /cc@dunglas@nicolas-grekas |
dunglas commentedAug 16, 2020
AFAIK it's still an issue. |
fabpot commentedAug 16, 2020
@dunglas Ok, can you rebase so that we can merge? |
116110a to3b034cbComparefabpot commentedAug 17, 2020
Thank you@dunglas. |
Currently, a bug prevents to configure the context keys to exclude from the cache key computation. The value is always replaced in the constructor. This PR fixes the problem.