Add PSR-20 Clock Interface as composer dependency

Created on 14 July 2025, 2 months ago

Problem/Motivation

PSR-20 defines a standard interface for system clocks.

If it implemented PSR-20, the service could be used with other libraries that can use a PSR-20 clock. And so it would encourage service reuse, add interoperability with other libraries, and prevent having multiple implementations on the same website.

Dependency Evaluation - psr/clock

Maintainership of the package

Maintained by PHP-FIG. Drupal already uses a number of similar packages, either directly (psr/log) or through other dependencies such as guzzle (psr/http-client) or symfony (psr/container, etc.)

Security policies of the package

Not sure it's relevant since it's only a single interface

Expected release and support cycles

Unlikely to require frequent updates, except for language evolution, e.g. updating syntax or signatures.

Code quality

The interface is too simple for this to be applicable, see https://github.com/php-fig/clock/blob/master/src/ClockInterface.php

Other dependencies it would add, if any (the full tree, not just direct dependencies), and evaluations for those dependencies as well

N/A

Proposed resolution

Add a composer dependency on psr/clock

Remaining tasks

Follow up with ✨ Implement PSR-20 in datetime.time service Active to add the implementation.

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

✨ Feature request

Status

Active

Version

11.0 🔥

Component

base system

Created by

🇦🇺Australia kim.pepper 🏄‍♂️🇦🇺Sydney, Australia

Live updates comments and jobs are added and updated live.

Needs framework manager review
It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

Needs release manager review
It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

Comments & Activities

Issue created by @kim.pepper
@kimpepper opened merge request.
Comment 2 months ago →
🇦🇺Australia kim.pepper 🏄‍♂️🇦🇺Sydney, Australia
As suggested by @catch I've split off adding the composer dependency to reduce the rebase burden.
Comment 21 days ago →
🇦🇺Australia kim.pepper 🏄‍♂️🇦🇺Sydney, Australia
Comment 14 days ago →
needs-review-queue-bot
The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024