- Issue created by @jurgenhaas
-
jurgenhaas →
committed 3bb22ea5 on 2.0.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed 3bb22ea5 on 2.0.x
-
jurgenhaas →
committed 13be8015 on 2.0.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed 13be8015 on 2.0.x
- 🇩🇪Germany jurgenhaas Gottmadingen
This is fixed for 2.x and will now be back ported to 1.1.x
-
jurgenhaas →
committed f4932460 on 1.1.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed f4932460 on 1.1.x
-
jurgenhaas →
committed 9a8d81bc on 1.1.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed 9a8d81bc on 1.1.x
-
jurgenhaas →
committed 65ddebdb on 1.1.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed 65ddebdb on 1.1.x
- 🇨🇭Switzerland Berdir Switzerland
Are you sure it's good idea to extend the core state class? What exactly is the purpose of this, does caching really make sense combined with that timestamp business?
Setting undefined properties will give you PHP deprecation warnings on 10.2
-
jurgenhaas →
committed fdb017bf on 2.0.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed fdb017bf on 2.0.x
-
jurgenhaas →
committed 53ae52d3 on 1.1.x
Issue #3437321: Add support for cache collector for state in core
-
jurgenhaas →
committed 53ae52d3 on 1.1.x
- Status changed to Fixed
5 months ago 9:52am 1 April 2024 - 🇩🇪Germany jurgenhaas Gottmadingen
You're right, thanks. The tests for ECA 1.1 with Drupal 10.2 have been failing too for that matter. I've fixed that such that for ECA 1.1 we do inject the extra services but don't do anything with them. That way, this code works for Drupal 10.2 and 10.3 likewise.
Automatically closed - issue fixed for 2 weeks with no activity.