-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Support PropertyBag in CRM_Utils_Array #16699
Conversation
(Standard links)
|
Hmm - looks like Core_menu needs to case to an array |
Retest this please |
@eileenmcnaughton checking the console output, this appears to have triggered the deprecation notice 32 times. |
test this please |
test this please |
1 similar comment
test this please |
We now use the PropertyBag in payment processors - but as @mattwire discovered the CRM_Utils_Array::value function is commonly used to access values now potentially 'in the bag' and the 'is_array' filtering here means it is not being returned
@colemanw I've pulled out the attempt to deprecate passing in non-arrays. It became clear it wasn't just a few outliers that were doing that & it was getting into a silly scope situation |
@colemanw @eileenmcnaughton Small follow-up PR #16737 so that array value still works on array access objects in the same way as it does for arrays. |
…ollowup CRM_Utils_Array::values follow up from #16699
Overview
We now use the PropertyBag in payment processors - but as @mattwire discovered the CRM_Utils_Array::value
function is commonly used to access values now potentially 'in the bag' and the 'is_array'
filtering here means it is not being returned
Before
Support PropertyBag in CRM_Utils_Array::value does not return values from the PropertyBag
After
Values returned - note we will encourage devs to move to direct access
Technical Details
Comments
discussion https://chat.civicrm.org/civicrm/pl/aygaho49jff5tqgar9erow7dew