Deprecated function: Creation of dynamic property

Patch created for above issue

Thank you.

Task for any upstream breaking changes.

FYI, regarding the failed test, Drupal 10 requires PHP8+. Do no select PHP7 as useless tests.

We'll need to fix it once for the entire ecosystem. Please move your patch to Blazy as mentioned here:
https://www.drupal.org/project/splide/issues/3338709#comment-14904569

Patch #2 works for me.

@gausarts
BlazyFilterBaseuses $blazyAdmin as property and its type is \Drupal\blazy\Form\BlazyAdminInterface (https://git.drupalcode.org/project/blazy/-/blob/8.x-2.x/src/Plugin/Filte...) meanwhile SlickFilter uses $admin with type \Drupal\slick\Form\SlickAdminInterface.

Seen these differences I don´t think it´s an easy change to be made in Blazy without breaking something else.

Due it´s a all ecosystem change, where should I create an issue to fix this? After checking the code for a while, I think that doing it in Blazy could involve huge changes that should be discused.

No problem at all, 100% :)

It is only registering the property. Properties can be inherited/ overriden just as classes or even services.

$blazyAdmin is already reserved by Blazy. We left it as is.
$admin is always open, generic, for any sub-modules. Blazy doesn't care nor use it. It just provides it quickly to DRY for many of its sub-modules since updating each sub-modules for the exact same change may take more time and energy. This will be provided by your patch above, only should be in Blazy.

The same patterns can be seen anywhere else:
$blazyManager for Blazy, $manager for its sub-modules, etc.

Let me know if anything else?

Please move your patch to Blazy as mentioned in the above link, #3. Just change @var to says \BlazyAdminInterface.

Thanks.

Same issue here filling up the logs. Did anyone already create that issue / patch at Blazy?