[12.x] Add Model::query($fetchModes) syntactic sugar #54745
Draft
Conversation
This file contains 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
| * @return \Illuminate\Database\Eloquent\Builder<static> | ||
| */ | ||
| public static function query() | ||
| public static function query(?array $fetchModes = []) |
There was a problem hiding this comment.
Why ?array?
Can it be null?
| * @return \Illuminate\Database\Eloquent\Builder<static> | ||
| */ | ||
| public function newModelQuery() | ||
| public function newModelQuery(?array $fetchModes = []) |
There was a problem hiding this comment.
This is a breaking change that was avoided in @bert-w 's PR.
We think that PR was ok just that it deleted a function that generated a bug and so the whole feature was reverted.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Follow-up to #54734 resp. #54443
Based on comments #54734 (comment) and #54443 (comment)
You can then do
without an additional call to
fetchUsing()As bert-w has pointed out, this only applies to queries created via a model's
query()method (or other public methods in that chain), so it may not be an alternative for all cases.