chore(HttpCache): outsource cache tag collection into normalizer events #5753
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.
This PR outsources the collection of cache tags for HTTP cache into individual events triggered from the normalizers instead of hardcoding into the the normalizers. This allows users to override or extend the cache tag logic with their own implementation.
This is related to #5650, where I brought up the idea:
The same events could later be extended for other purposes where we need to trigger side effects during normalization (e.g. to collect push resources). And of course can be used by users for other user specific business logic.
Should this be documented somewhere? And if so, where and how?