Make nullable parameter types explicit to avoid deprecation warnings #1013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What’s been done
Just a quick tidy-up.
PHP 8.1 started warning about implicitly nullable parameters, and PHP 8.4 is going to make them a hard error.
So I’ve updated the function signatures to use
?type
syntax explicitly.Before:
After:
This keeps us ahead of future PHP upgrades and makes the intent a bit clearer.
Shouldn’t affect any actual logic — purely a syntax-level fix.
Let me know if anything needs tweaking!