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

Skip to content

[FrameworkBundle] no serializer mapping cache in debug mode without enable_annotations #51497

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

Conversation

soyuka
Copy link
Contributor

@soyuka soyuka commented Aug 27, 2023

Q A
Branch? 5.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets #51497
License MIT
Doc PR not needed

There's no reason we should disable the cache only without enable_annotations, when working only with attributes, in debug mode the cache is enabled which is why we often need to clear cache when changing a serialized object to get the changes.

@fabpot
Copy link
Member

fabpot commented Aug 30, 2023

Please, keep the full header in the description.

…nable_annotations

There's no reason we should disable the cache only without `enable_annotations`, when working only with attributes, in debug mode the cache is enabled which is why we often need to clear cache when changing a serialized object to get the changes.
@soyuka soyuka force-pushed the fix/serializer-mapping-cache-debug branch from 2de525a to 4312e96 Compare September 13, 2023 07:14
@soyuka
Copy link
Contributor Author

soyuka commented Sep 13, 2023

done I guess you spoke about the commit description

@nicolas-grekas
Copy link
Member

Thank you @soyuka.

@nicolas-grekas nicolas-grekas merged commit e065f2e into symfony:5.4 Sep 14, 2023
This was referenced Sep 30, 2023
@bastnic
Copy link
Contributor

bastnic commented Nov 6, 2024

The reason is that for yaml/xml, it's ban by CachePoolClearerCacheWarmer (from apip...) from this PR https://github.com/symfony/symfony/pull/35109/files.

With that PR, it means that all yaml/xml are parsed at each request without any change :(.

@xabbuh
Copy link
Member

xabbuh commented Nov 8, 2024

@bastnic comments on merged PRs are likely to get lost. Please open a new issue if you think that you discovered an issue with this implementation and provide a small example application that allows to reproduce it.

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.

8 participants