N°7213 - PHP 8.1: Migrate remaining usages of md5() with null value #608
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.
Base information
Symptom (bug)
Deprecation notice in the logs
Reproduction procedure (bug)
No real use case so far, only programatically with the following delta.
Cause (bug)
In some cases, the
$m_data
property of the\ormDocument
can be null and cause this. But how it can be null is not clear yet.Proposed solution (bug and enhancement)
Protect code by using the coalesce operator (
??
) to use''
instead of null in themd5()
.My opinion was that the 2 usages are for fingerprint / signature / cache buster, so we should return a signature even for an empty content as when the content would change, it signature / fingerprint will as well.
\ormDocument::GetSignature()
:AttributeBlob::Fingerprint()
Checklist before requesting a review
Checklist of things to do before PR is ready to merge
None