Would be cool if we could maybe kick off a 2.x branch and make it D10 ready.

Here's the report: https://dev.acquia.com/drupal10/deprecation_status/projects/phpstorm_met....

Info file, of course. And some Drush deprecations.

CommentFileSizeAuthor
#6 phpstorm_metadata-3330783-drupal-10-readiness_1.diff2.76 KBmurz

Issue fork phpstorm_metadata-3330783

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:

About issue forks

Comments

leymannx created an issue. See original summary.

Murz made their first commit to this issue’s fork.

Murz opened merge request !2

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented
Status: Active » Needs review

I've fixed all remarks from Drupal 10 deprecation details report, please review.

teebeecoder’s picture

teebeecoder commented
Status: Needs review » Reviewed & tested by the community

Hi, I tested the patch on a fresh instance and after enabling the module, no errors shown in DB log and the file was generated correctly.

So LGTM.

Thomas

murz’s picture

murz
Primary language English
Location Yerevan, Armenia
commented
StatusFileSize
new phpstorm_metadata-3330783-drupal-10-readiness_1.diff2.76 KB

Attaching a static patch file with those changes, to make it possible to use in composer until #3204538: GitLab Merge Requests Unable to Generate Incremental Patch Files is resolved.

undertext’s picture

undertext commented
Status: Reviewed & tested by the community » Fixed

Thanks for the patch!
Merged to 8.x-1.x.

Status: Fixed » Closed (fixed)

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

norman.lol’s picture

norman.lol
he/him
Primary language German
Location Berlin
commented

We need a release 🙏🏻