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

Make nullable parameters explicity nullable for PHP 8.4 #111

Closed

Conversation

emteknetnz
Copy link

Copy link
Member

@WyriHaximus WyriHaximus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, thanks for taking the time to address this. Did find something that requires updating due to the PHP versions in range

@@ -164,7 +164,7 @@ public function __construct($cmd, $cwd = null, array $env = null, array $fds = n
* @param float $interval Interval to periodically monitor process state (seconds)
* @throws \RuntimeException If the process is already running or fails to start
*/
public function start(LoopInterface $loop = null, $interval = 0.1)
public function start(?LoopInterface $loop = null, $interval = 0.1)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you update this method the same way this method has been updated in another package? https://github.com/reactphp/socket/pull/318/files#diff-2c0b16424077d1ecafdbbca23aa3f137bc007241b00fe55dd536434c147326ca This way we can ensure it runs on all PHP versions in rage

Copy link
Member

@clue clue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emteknetnz Thanks for looking into this. I've just replied with a status update in #110 and plan to get this in for the next release.

Unfortunately this requires a bit more work to support legacy PHP versions as suggested in #108. The good news is, we've already prepared all the required changes there and only need to backport this as discussed in #110.

Once #113 is merged, we can move forward with this. In the meantime, I don't think there's much that needs to be done here. I'll get back to this once we make progress.

@WyriHaximus
Copy link
Member

Closing this PR as it has been resolved through #114

@clue clue removed this from the v0.6.6 milestone Jan 1, 2025
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.

3 participants