Automated tests currently report a number of validation issues that should be fixed.

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

justin2pin created an issue. See original summary.

  • justin2pin committed c97badfb on 2.1.x
    Issue #3502083: Fix validation issues for automated testing
    
justin2pin’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

maursilveira’s picture

Hello,

Thank you for this module, it's extremely handy!

Any idea of when a new release could be created including the fixes from this issue? I'm using 2.1.1, and what I'm really looking for is the fix for the following PHP 8.4 deprecations:

Deprecated: Drupal\layout_paragraphs\Form\EditComponentForm::buildForm(): Implicitly marking parameter $layout_paragraphs_layout as nullable is deprecated, the explicit nullable type must be used instead in /app/web/modules/contrib/layout_paragraphs/src/Form/EditComponentForm.php on line 21

Deprecated: Drupal\layout_paragraphs\Form\EditComponentForm::buildForm(): Implicitly marking parameter $component_uuid as nullable is deprecated, the explicit nullable type must be used instead in /app/web/modules/contrib/layout_paragraphs/src/Form/EditComponentForm.php on line 21

Deprecated: Drupal\layout_paragraphs\Form\DeleteComponentForm::buildForm(): Implicitly marking parameter $layout_paragraphs_layout as nullable is deprecated, the explicit nullable type must be used instead in /app/web/modules/contrib/layout_paragraphs/src/Form/DeleteComponentForm.php on line 63

Deprecated: Drupal\layout_paragraphs\Form\DeleteComponentForm::buildForm(): Implicitly marking parameter $component_uuid as nullable is deprecated, the explicit nullable type must be used instead in /app/web/modules/contrib/layout_paragraphs/src/Form/DeleteComponentForm.php on line 63

Thank you!

chewi3’s picture

Ended up here also looking for a fix for the deprecation warnings. I created a patch that might also be of use to others. It includes specifically the deprecation fixes (for 2.1.1). It does not contain the other changes from this merge. For that you can download the plain diff from the commit.

anybody’s picture

@justin2pin sorry to disturb, but 1 year later 2.1.1 is still the latest stable release and has these PHP deprecation warnings. Would be great if a new tagged release could be published to fix this. PHP 8.4 is widely used and in the meantime several duplicate issues popped up for that reason.

Thanks!!

anybody’s picture

@justin2pin could you please please please tag a new 2.1.2 release based on the latest dev containing these fixes?
Projects with PHP 8.4 fill their logs with all these deprecations.

That would be super helpful, thank you!

anybody’s picture

Issue tags: +PHP 8.4
clairero’s picture

Also came here to say that it would be great to have a new release that includes the PHP 8.4 deprecation fixes. We're currently using module version 2.1.1 . It would be ideal to have a new release tagged.

anybody’s picture

@clairero thanks. I already wrote @justin2pin a PM but think he's very busy - didn't get a reply yet. But I think he'll surely tag a new release asap.