RA.isTrue, RA.isFalse

[char0n]

Don't forget to refactor code that now uses constructs like

equals(true)
equals(false)

[rockymadden]

I can grab this one, have it in a handful of private repos that I can then leverage against.

[char0n]

Go for it... don't forget to process 1st comment of this issue though

[rockymadden]

Yep, got it.

[char0n]

@rockymadden will you be able to squeeze something at least of them in for v2.3.0 release ?

[rockymadden]

@char0n Yep, I can get that done by the 14th.

[rockymadden]

@char0n Family and work has come up. I will not be able to finish by tomorrow.

[char0n]

Np, don,t worry

…

Sent from my iPad

On 13 Jan 2018, at 21:01, Rocky Madden ***@***.***> wrote: @char0n Family and work has come up, despite my best efforts. I will not be able to finish by tomorrow. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Undistraction]

If we had this in we could also add propIsTrue and propIsFalse. Basically:

const propIsTrue = propSatisfies(isTrue)
const propIsFalse = propSatisfies(isFalse)

But I guess if we go down that road then where do we stop? propIsArray, propIsString etc

[char0n]

@Undistraction I would go this way if we find enough usecases in our codebases. If there are no usecases for us at this moment (I don't have one now) I'd rather wait for somebody to request it or for us having a usecases for it.

[char0n]

@rockymadden assigned this to v2.4.0 milestone. Let's see if we manage to implement at least one of them ;]

[Undistraction]

@rockymadden You OK if I pick this up?