Closed (fixed)
Project:
Search API
Version:
8.x-1.x-dev
Component:
Tests
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
5 Jan 2025 at 16:26 UTC
Updated:
6 Feb 2025 at 08:24 UTC
Jump to comment: Most recent
Comments
Comment #3
drunken monkeySeems these are just deprecation warnings caused by other contrib modules. We can just ignore them here, they should be fixed in the respective modules (see #3496037: Fix implicitly nullable parameter type hints and #3497583: Fix deprecated implicitly nullable types).
I created an MR, let’s see if pipelines pass now (resp. report the one new deprecation I added for testing purposes).
Comment #4
drunken monkeyHuh. No idea why that didn’t work.
Especially: Why did the PHP 8.4 tests not report the newly added implicitly nullable type?
Trying again with a different regex.
Comment #5
drunken monkeyStill didn’t work.
Well, those should be resolved by the other modules anyways, so we can live with them for a week or two.
On the other hand, I now tried to fix the reported deprecations against Drupal 11.2 for using the deprecated
Entity::$originalproperty. Let’s see how that goes.Comment #6
solideogloria commentedHere's all the Search API errors I get when rebuilding the cache in PHP 8.4:
Edit: also these
Comment #7
solideogloria commentedThese are not from other contrib modules, so the method signatures need to be fixed and made explicitly nullable.
Comment #9
scott_euser commentedDeprecations raised in #6 are solved in this MR as far as I can see; are you sure you had the MR patch applied when rebuilding cache?
Fixed some more issues + suppressed the phpstan error from the backwards compatibility call (which is expected)
I don't understand the error from phpunit (next minor) though. Maybe something in the test coverage not properly UTF8 maybe?
Comment #10
solideogloria commentedI looked at the diff: https://git.drupalcode.org/project/search_api/-/merge_requests/208/diffs
It doesn't have a single changed method signature to add the nullable to the type.
Comment #11
scott_euser commentedBut they all have a ? infront of them already, maybe fixed somewhere against dev branch? Or maybe I'm misunderstanding the issue - very possible :)
Comment #12
solideogloria commentedThey must be already fixed in the dev branch, then.
Comment #15
drunken monkeyMerged.
Thanks for bringing this over the finish line, Scott!
Comment #16
liam morlandThanks. If max PHP testing is enabled, that would allow us to see that the nullable type deprecations have been fixed.
Comment #17
claudiu.cristeaI think we can add
OPT_IN_TEST_MAX_PHP: 1to see if we're PHP 8.4 readyComment #18
claudiu.cristeaComment #19
claudiu.cristeaCreated #3501639: PHP 8.4 compatibility for #17