`_isNumerical` implementation doesn't make sense about humps HOT 4 CLOSED

As, obviously, this code could never return false. You could replace the entire implementation with return true and it would behave the same way.

Not quite:

> NaN === NaN
false

Which I think is the intent, in which case it would perhaps be clearer for this function to be implemented as return !isNaN(obj - 0); or perhaps return !isNaN(+obj);.

from humps.

Ah yes I guess that could be it. Definitely should be using the explicit function for that - perhaps the Number.isNaN one though.

from humps.

Yep, there we go: #13 (diff)

Looks like that review comment was not addressed.

from humps.

Closing due to inactivity

from humps.