From b851ebc06c513eefa96d8c3fc97bf120d63b61e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marek=20Noco=C5=84?= Date: Mon, 13 Jul 2026 10:09:23 +0200 Subject: [PATCH] [v6] Reworked how content tagging works --- .../cache/http_cache/content_aware_cache.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md index f000188f1a..f9d5464d15 100644 --- a/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md +++ b/docs/infrastructure_and_maintenance/cache/http_cache/content_aware_cache.md @@ -147,13 +147,12 @@ The built-in taggers support the following value types: - Any view implementing `Ibexa\Core\MVC\Symfony\View\ContentValueView` - Any view implementing `Ibexa\Core\MVC\Symfony\View\LocationValueView` -!!! caution - - If a value of any other type is passed (for example, a [`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html) object), no tagger matches and the call has no effect. - ## DispatcherTagger -Accepts any value and passes it on to every tagger registered with the service tag `ibexa.cache.http.response.tagger`. +Accepts any value and passes it on to taggers registered with the service tag `ibexa.cache.http.response.tagger` supporting given type. + +If you pass a value which no tagger supports (for example, a [`Content`](/api/php_api/php_api_reference/classes/Ibexa-Contracts-Core-Repository-Values-Content-Content.html) object), the system logs a warning. +When [`kernel.debug`]([[= symfony_doc=]]/reference/configuration/kernel.html#kernel-debug) is enabled, an exception is thrown to help you catch unsupported types early. ## Response tagging in controllers