Remove implicit nullability deprecated in PHP 8.4 #269
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.
PHP 8.4 deprecates implicitly nullable parameters, i.e. typed parameter with a
null
default value, which are not explicitly declared as nullable.See https://wiki.php.net/rfc/deprecate-implicitly-nullable-types
Ideally, we would just change the type hint
?DOMElement
but https://wiki.php.net/rfc/nullable_types was only introduced in PHP 7.1, while we still support PHP 5.6.This patch is a somewhat hacky alternative to #264 that fixes those warnings without breaking backwards compatibility or removing PHP < 7.1 support. We remove the offending formal arguments in favour of obtaining them with
func_get_arg()
and checking their type ourselves. The PHPDoc param annotations were updated to match the actual types of the now virtual arguments.The downside is that it removes PHP 7.4’s parameter contravariance checks (https://wiki.php.net/rfc/covariant-returns-and-contravariant-parameters) so future re-introduction of the formal arguments would be a BC break.