Improvement handle falsy values in collections #55512
Draft
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.
Purpose
This PR adds a new valuePreservingFalsy method to Laravel Collections that safely retrieves a value for a given key without discarding falsy values like 0, false, '0', or an empty array.
Benefit to End Users
The existing value() method internally uses firstWhere(), which stops on the first truthy match—excluding valid falsy values such as 0 and false. This new method ensures that these legitimate values are preserved and returned when present.
Backward Compatibility
This is a new method, so it does not affect any existing functionality or break backward compatibility.
Tests Included
Example
$collection = collect([
['name' => 'Tim', 'balance' => 0],
['name' => 'John', 'balance' => 200],
]);
$collection->valuePreservingFalsy('balance'); // returns 0
Test coverage for all major PHP falsy values:
Related Issue
Closes #54910