Make type hints explicitly nullable (avoid deprecation from PHP 8.4) #11
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.
Hi! This is just a small PR to update a few typehints that are causing deprecation warnings starting with PHP 8.4 (released in November 2024). Sorry I’m not sure how to prefix the commit following the recommended notation.
Description
In order to fix a deprecation introduced in PHP 8.4, this makes explicit the "implicit nullable" type hints in function arguments.
For example:
This generates a deprecation warning.
The solution
The
$parametersargument is supposed to be an array, but its default value is null, so its actual type is "array or null". We need to make it explicit by prefixing the type with a question mark (anull|arrayunion type would work too):See https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated
Summary by Sourcery
Update type hints to explicitly mark nullable parameters to resolve PHP 8.4 deprecation warnings
Bug Fixes:
Enhancements: