- Issue created by @kim.pepper
- @kimpepper opened merge request.
- 🇦🇺Australia kim.pepper 🏄♂️🇦🇺Sydney, Australia
As suggested by @catch I've split off adding the composer dependency to reduce the rebase burden.
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.
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.)
Not sure it's relevant since it's only a single interface
Unlikely to require frequent updates, except for language evolution, e.g. updating syntax or signatures.
The interface is too simple for this to be applicable, see https://github.com/php-fig/clock/blob/master/src/ClockInterface.php
N/A
Follow up with ✨ Implement PSR-20 in datetime.time service Active to add the implementation.
Active
11.0 🔥
base system
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.
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.
As suggested by @catch I've split off adding the composer dependency to reduce the rebase burden.