[13.x] Fix scope removal in nested where conditions#54816
Merged
taylorotwell merged 3 commits intolaravel:masterfrom Feb 27, 2025
Merged
[13.x] Fix scope removal in nested where conditions#54816taylorotwell merged 3 commits intolaravel:masterfrom
taylorotwell merged 3 commits intolaravel:masterfrom
Conversation
crynobone
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If you remove a scope in a nested where condition, it is never copied over from the nested query builder and applied to the root query builder. This would happen when calling a scope like
onlyTrashed, which removes the global soft deletes scope, in a nested where.This could possibly be a breaking change since scopes that were previously not removed would start being removed.