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
but it was not clear to me why the assert is needed there, actually in my case instead of the assert(res == x) I had a scalatest.Assertion and it kept asking me for an implicit IO[Assertion] => PropF[F] which i found very hard to do.
I solved it by using PropF.boolean but it took a while to discover that this is probably what i should use.
Now if I am not missing anything else, I think this would we much more intuitive:
@adrian-salajan Apologies on the delay in response. I think supporting IO[Boolean] is a good idea. We currently support IO[Unit] so the original could have been .map(res => res shouldBe 42).void
A PR for this got merged, but I forgot to add the Closes #25 :
Also, this is a gentle request for a release, so that I can advocate this lib at work :D
Hello, today I tried using this lib, from the provided example:
but it was not clear to me why the assert is needed there, actually in my case instead of the assert(res == x) I had a scalatest.Assertion and it kept asking me for an implicit IO[Assertion] => PropF[F] which i found very hard to do.
I solved it by using PropF.boolean but it took a while to discover that this is probably what i should use.
Now if I am not missing anything else, I think this would we much more intuitive:
with the help of
then the user can map any F[A] to F[Boolean]
WDYT ?
If ok i can try a PR.
The text was updated successfully, but these errors were encountered: