Explicitly listed types supported by Response Tagger#3109
Open
Explicitly listed types supported by Response Tagger#3109
Conversation
Preview of modified filesPreview of modified Markdown: |
mnocon
commented
Mar 30, 2026
docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md
Outdated
Show resolved
Hide resolved
|
code_samples/ change report
|
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
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.



As mentioned on the community Slack, the doc should list the available types to make this less confusing.
If an experienced Symfony developer who reads the doc still make mistakes when using the API, then it must be confusing.
In addition, I think we should consider improving the DX by making changes directly in the ibexa/http-cache package, for example by:
Report:

Answer:
Feedback:
