minor #18510 [FrameworkBundle] Remove terminate_on_cache_hit option (OskarStark)

javiereguiluz · javiereguiluz · commit 1fc0bed1535c · 2023-07-05T14:35:14.000+02:00
This PR was merged into the 7.0 branch. Discussion ---------- [FrameworkBundle] Remove `terminate_on_cache_hit` option Refs * #18491 Commits ------- e6f6bbd Remove `terminate_on_cache_hit` option.
diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
@@ -167,27 +167,6 @@ which the cache can serve a stale response when an error is encountered
 (default: 60). This setting is overridden by the stale-if-error HTTP
 Cache-Control extension (see RFC 5861).
 
-terminate_on_cache_hit
-......................
-
-**type**: ``boolean`` **default**: ``true``
-
-If ``true``, the :ref:`kernel.terminate <component-http-kernel-kernel-terminate>`
-event is dispatched even when the cache is hit.
-
-Unless your application needs to process events on cache hits, it's recommended
-to set this to ``false`` to improve performance, because it avoids having to
-bootstrap the Symfony framework on a cache hit.
-
-.. versionadded:: 6.2
-
-    The ``terminate_on_cache_hit`` option was introduced in Symfony 6.2.
-
-.. deprecated:: 6.2
-
-    Setting the ``terminate_on_cache_hit`` option to ``true`` was deprecated in
-    Symfony 6.2 and the option will be removed in Symfony 7.0.
-
  .. _configuration-framework-http_method_override:
 
 http_method_override
