Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2.x] Improve PHP 8.4+ support by avoiding implicitly nullable types #165

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

clue
Copy link
Owner

@clue clue commented Dec 27, 2024

This changeset backports #157 and #164 from 3.x to 2.x to improve PHP 8.4+ support by avoiding implicitly nullable types as discussed in reactphp/promise#260. The same idea applies, but v2 requires manual type checks to support legacy PHP versions as the nullable type syntax requires PHP 7.1+ otherwise.

Note that the test suite may still report some harmless warnings for v2 on PHP 8.4 as it still uses the legacy clue/reactphp-block package. For v3 this has been replaced with reactphp/async with #149, but I would argue it's probably not worth the effort backporting all related changes just to fix an otherwise harmless warning in the v2 test suite. Instead, updating to v3 should be the way forward.

Builds on top of #157, #164, #151, #114, reactphp/promise#260, reactphp/socket#318, clue/redis-protocol#19, reactphp/promise-timer#70 and clue/framework-x#267

@clue clue added this to the v2.8.0 milestone Dec 27, 2024
@clue clue merged commit e2a4cfb into clue:2.x Dec 27, 2024
15 checks passed
@clue clue deleted the nullable-v2 branch December 27, 2024 16:33
This was referenced Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant