What about adapters?

What about adapters?

#275 solves this issue for most of them (Chain and Common still need to be updated).

I had some free time, so I played with the psr/*:3.x compatibility.
Here is the result:

• Sweetchuck-psr-cache/*
• Sweetchuck/cache-backend-arangodb

Originally cache/cache is a mono repo, which contains multiple projects.

git ls-files '**/composer.json'

src/Adapter/Apc/composer.json
src/Adapter/Apcu/composer.json
src/Adapter/Chain/composer.json
src/Adapter/Common/composer.json
src/Adapter/Doctrine/composer.json
src/Adapter/Filesystem/composer.json
src/Adapter/Illuminate/composer.json
src/Adapter/Memcache/composer.json
src/Adapter/Memcached/composer.json
src/Adapter/MongoDB/composer.json
src/Adapter/PHPArray/composer.json
src/Adapter/Predis/composer.json
src/Adapter/Redis/composer.json
src/Adapter/Void/composer.json
src/Bridge/Doctrine/composer.json
src/Bridge/SimpleCache/composer.json
src/Encryption/composer.json
src/Hierarchy/composer.json
src/Namespaced/composer.json
src/Prefixed/composer.json
src/SessionHandler/composer.json
src/TagInterop/composer.json
src/Taggable/composer.json
src/Util/composer.json

And some how it is sliced into several individual projects.

• cache/adapter-common
• cache/hierarchical-cache
• cache/integration-tests
• ...

Maybe it is easier to maintain a mono repo, but difficult to use the derivated individual projects. For example if you need to apply a patch.

I don't think that codes from Sweetchuck-psr-cache/* repositories ever gonna gets merged into the upstream repository, but it might be a good starting point to implement the psr/*:3.x compatibility.

Drupal 10 Requires psr/cache: ^3, and adapters don't seem to get me around that fact while apcu-adapter still requires 1 || 2. Could this move forward so that sites can continue to be updated?

do you guys see any chance of moving this PR forward?

having the same issue as @rreedy
trying to install cache/array-adapter on a Drupal 10 but the psr/cache requirements are locked to ^1.0 || ^2.0