-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Implement value retrieval and checks by predicate callback #142
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #142 +/- ##
=========================================
Coverage 99.76% 99.77%
- Complexity 214 226 +12
=========================================
Files 4 4
Lines 429 445 +16
=========================================
+ Hits 428 444 +16
Misses 1 1 ☔ View full report in Codecov by Sentry. |
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.
Can you fix psalm errors? Seems it shows problems in code...
142b6d0
to
ff4a7fa
Compare
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.
Now closure will be inconsistent in getValue()
and other methods:
toArray()
index()
getColumn()
map()
Is there real case for getValue()
with closure that implement in current PR?
There is a PHP RFC: array_find and its PR that is what actually I need to be implemented. It seems has been discussed about a month ago and I found exactly it just now. Thank you in advance for taking your time. |
It's interesting. May be we keep ArrayHelper::find()
ArrayHelper::findKey()
ArrayHelper::any()
ArrayHelper::all() |
Yes makes sense. |
I'll continue with it |
done |
closes #135