[8.x] Compatibility between EnumeratesValues and BuildsQueries on when() method #36217
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.
This simple PR aims to ensure compatibility between
src/Illuminate/Collections/Traits/EnumeratesValues.phpandsrc/Illuminate/Database/Concerns/BuildsQueries.phponwhen()method.Before, using
when()method on collection without returning value, lead to collection being null (user must always return the same collection to chain further methods). This is understandable, but when we're doing the same thing inside query builder, we may return nothing (null) and Laravel corrects us returning builder again:framework/src/Illuminate/Database/Concerns/BuildsQueries.php
Lines 208 to 210 in a6680d9
This leads to confusion in my opinion.
Thank you for reading.