If adding garbage collection to L1 I think this should be also called in the integration layer's garbage collection. At the moment it is calling only L2's garbage collection.

@ndobromirov:

If adding garbage collection to L1 I think this should be also called in the integration layer's garbage collection. At the moment it is calling only L2's garbage collection (GC).

The interface is mostly for testing so it's possible to create an item, have it expire, run GC, and finally verify that it gets GCed. SQLiteL1 already runs GC in its destructor, so library consumers don't have to do anything.

Now, I'd prefer to move L1 GC into something that runs outside requests, but there's no concept in most CMS interfaces to run something locally on each web server or container, which would be required. The destructor is not so bad, anyway, as it runs after PHP-FPM has closed the request response.

To avoid confusion, I've removed the collectLocalGarbage() method from Integrated.

Coverage remained the same at 100.0% when pulling 1bc0706 on sqlite-l1 into 91f739d on master.

Coverage remained the same at 100.0% when pulling daf7d1f on sqlite-l1 into 91f739d on master.