Issue Task Resolved

#110638Restrict cache backend default lifetime setter visibility

Wouter Wolters 09/06/26, 08:35 updated 09/07/26, 08:05

Description

AbstractBackend::setDefaultLifetime() is currently public even though it is
an internal configuration setter. Cache backends already configure the default
lifetime through their constructor options.

The only direct Core usage outside the configuration mechanism is in Redis
functional tests. Those tests should use the supported defaultLifetime
constructor option instead.

The setter can then be made protected, preventing it from being used as a
runtime API. A redundant Redis lifetime test can also be removed.

Reviews 1

History 12

  1. Wouter Wolters commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-07T08:05:09+00:00" > 09/07/26, 08:05 </span>

    Applied in changeset commit:9c170a0f7a1c5fa4ce8bb09dee6eb2a9a757cfbe.