ScalaUtils `Or` could really use a `bmap` about scalatest HOT 6 CLOSED

A bad-map. Interesting and makes sense. Just for context, can you give a specific example where you want to keep the good side the same if it is good, but transform the bad if it is bad?

from scalatest.

Sure. A bit contrived but you get the idea:

def findUser(id: Long): User Or ErrorCode = ???

findUser(123).bmap {
  case Missing => "User was not found"
  case Error => "Internal error, please try again later"
}

Also when integrating with Try

def findUser(id: Long): Try[User] = ???

Or.from(findUser(123)).bmap {
  case exc: MissingValueException => "User was not found"
  case _: Throwable => "Internal error, please try again later"
}

from scalatest.

So basically when you need to transform the error as it is passing through is my biggest use case.

from scalatest.

Hi Jason,

I see. Makes sense. I'll add something like that in the next release.

Bill

On Fri, Dec 13, 2013 at 10:30 AM, Jason Webb [email protected]:

Sure. A bit contrived but you get the idea:

def findUser(id: Long): User Or ErrorCode = ???
findUser(123).bmap {
case Missing => "User was not found"
case Error => "Internal error, please try again later"}

Also when interpolating with Try

def findUser(id: Long): Try[User] = ???
Or.from(findUser(123)).bmap {
case exc: MissingValueException => "User was not found"
case _: Throwable => "Internal error, please try again later"}

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/197#issuecomment-30531848
.

Bill Venners
Artima, Inc.
http://www.artima.com

from scalatest.

Awesome thanks! And thanks for ScalaUtils. I love it.

from scalatest.

I have checked a badMap method for Or into the 2.1.x branch, which is queued to go out as 2.1.0 final shortly. It is also merged into master. I also added a fold method. Thanks for the suggestion.

from scalatest.