Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Current run on PHP 8.2 beta1 at Drupal-CI produces tremendously huge logs (>2GB) but applying new attributes and remove them later in #3299855: [META] Get rid of #[\AllowDynamicProperties] attribute to give contrib to not abuse CI system logs while testing under 8.2 containers
Steps to reproduce
- attribute annotation + vfs fix https://dispatcher.drupalci.org/job/drupal_patches/139371/artifact/jenki...
Proposed resolution
5 classes needs this attribute and follow-ups to fix it properly
core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php
#3299857: [PP-1] Remove AllowDynamicProperties attribute from ConfigEntityBasecore/lib/Drupal/Core/Extension/Extension.php
#2024043: Add Module, Theme, Profile, and Extension value objectscore/modules/views/src/Plugin/views/PluginBase.php
#3299858: Remove AllowDynamicProperties attribute from views/PluginBasecore/modules/views/src/Plugin/views/join/JoinPluginBase.php
#3299859: Remove AllowDynamicProperties attribute from JoinPluginBasecore/modules/views/src/ResultRow.php
#3275858: View's ResultRow uses deprecated dynamic properties
Remaining tasks
review/commit
User interface changes
no
API changes
no
Data model changes
no
Release notes snippet
no
Comment | File | Size | Author |
---|---|---|---|
#2 | 3299853-2.patch | 2.19 KB | andypost |
Comments
Comment #2
andypostComment #3
andypostFiled follow-up plan #3299855: [META] Get rid of #[\AllowDynamicProperties] attribute
Comment #4
andypostComment #5
andypostComment #6
kim.pepper+1 This seems like a sensible way to manage the transition away from dynamic properties.
Comment #7
catchMakes sense to me.
Comment #8
kim.pepperComment #10
catchCommitted/pushed to 10.1.x and cherry-picked to 10.0.x, thanks!
Comment #12
catchCherry-picked to 9.5.x too.