-
Notifications
You must be signed in to change notification settings - Fork 11.7k
get and has method else removed (re-submission) #24032
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -294,11 +294,11 @@ public static function get($array, $key, $default = null) | |
| } | ||
|
|
||
| foreach (explode('.', $key) as $segment) { | ||
| if (static::accessible($array) && static::exists($array, $segment)) { | ||
| $array = $array[$segment]; | ||
| } else { | ||
| return value($default); | ||
| if (!static::accessible($array) || !static::exists($array, $segment)) { | ||
| return value($default); | ||
| } | ||
|
|
||
| $array = $array[$segment]; | ||
| } | ||
|
|
||
| return $array; | ||
|
|
@@ -335,11 +335,11 @@ public static function has($array, $keys) | |
| } | ||
|
|
||
| foreach (explode('.', $key) as $segment) { | ||
| if (static::accessible($subKeyArray) && static::exists($subKeyArray, $segment)) { | ||
| $subKeyArray = $subKeyArray[$segment]; | ||
| } else { | ||
| return false; | ||
| if (!static::accessible($subKeyArray) || !static::exists($subKeyArray, $segment)) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is a change in this condition needed?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See the previous comment . |
||
| return false; | ||
| } | ||
|
|
||
| $subKeyArray = $subKeyArray[$segment]; | ||
| } | ||
| } | ||
|
|
||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is a change in this condition needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cause Previously it was both of them needs to be true. If any of them turns to
falsethe condition check will fail. As we are inverting it, so we need to check either one isfalseor not. Hope you get it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see a few problems with this:
For me is more natural to read "if accessible and exists" as "if not accessible or not exists".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh... It's not a problem actually, it's may be your personal preference 😃 Anyway, to me it's more readable than the one with
else. Also, earlyreturnis preferable I think and we try to follow it in other parts of Laravel code base.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well for me if the element is not accessible there are more chances that it does not exist, this will mean that the second condition will be always evaluated when not needed.
With the previous code, it was clear that after an array is not accessible we will return the default value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uha... Good point! 👍 Need to give it a shot! Thinking about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By inverting the condition position we can solve this issue @jmarcher 🤔. See my last commit.