You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having trouble reproducing, when i pass in null object propOr throws an error because it's trying to read a property off an object that doesn't exist. Seems to function as I would expect when the value stored at the accessed property is both null and undefined.
correct, in my opinion it should behave the same as pathOr which reads the object and if that object does not exist (undefined or null) it returns the defaulted value.
Describe the bug
propOr
is falling over on null values, this feels like a deja vu bug?To Reproduce
Steps to reproduce the behavior:
propOr
propOr('', ['name'], null)
Expected behavior
I believe propOr should return the default value on a null just like it would for undefined
The text was updated successfully, but these errors were encountered: