feat(doctrine): improve http cache invalidation using the mapping #7319
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
that's really nice! |
|
#7300 merged! |
mrossard
force-pushed
the
feat-cache-invalidation-using-mapping
branch
4 times, most recently
from
15a07e1 to
88b160c
Compare
mrossard
force-pushed
the
feat-cache-invalidation-using-mapping
branch
from
88b160c to
ea26095
Compare
|
If i'm not mistaken the test errors i get are not related... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to the new ObjectMapper integration we have an "easy" way to fetch an ApiResource impacted by changes on a doctrine entity.
It makes it possible to greatly improve http cache invalidation, which is currently done in a doctrine listener, when using stateOptions.
This is not yet tested - this probably can't yield correct results without #7300 anyway.