Hi, someone could tell me? please, why I get this error:
Cannot materialize pickler for non-case class: Either[String,T]. If this is a collection, the error can refer to the class inside.
[error] val unPickle = Unpickle[Either[String, T]].fromBytes(value)with this code:
def searchDescripCatalog[T](id: String, component: Handler[String], resource: String) = {
val payload = Pickle.intoBytes[String](id)
val respondWS = client.send(resource :: Nil, payload, SendType.WhenConnected, 30 seconds)
respondWS.failed.foreach(println)
respondWS.onComplete {
case Success(value) =>
value match {
case Right(value) =>
val unPickle = Unpickle[Either[String, T]].fromBytes(value)
unPickle match {
case Right(value) => component.onNext(value.descripcion.getOrElse(""))
case Left(error) =>
org.scalajs.dom.window.prompt(error)
}
case Left(value) => org.scalajs.dom.window.prompt(value)
}
case Failure(exception) => org.scalajs.dom.window.prompt(exception.getMessage)
}
}
Does anyone have an example of how to create a pickler for a collection, in my case
In other words, I can't seem to pickle any case class that contains a collection with a type not doesn't have default pickler.
immutable.TreeMap that contain types that don't already have a pickler?In other words, I can't seem to pickle any case class that contains a collection with a type not doesn't have default pickler.
note the collections changed a lot in 2.13, so there is a different implementation for that version
@ochrons is it a known/deliberate limitation, that case classes containing collections with certain types, won't generate automatically? In my case, it's a
TreeMap with LocalDate as key and a case class as value. I assume it's the LocalDate that's causing the issue, but even having a LocalDate pickler in scope doesn't seem to resolve the issue.
sometimes you just need to supply the pickler manually
good question
let's say
I am not sure what is the difference betwen the two
but basically
actuall
yes
but you know what
i think i just store Map[String,JSON]
and then problem is solved :)
and use circe
well
yeah
ideally :)
especially if boopickle was using binary codecs
we are trying to serialize like 200MB of data
it depends a lot on payload and environment... as an example jsoniter-scala can serialize with speed up to 3Gb/sec... please see the full picture here
Boopickle comes with a performance test suite that you can easily modify to match your data and see the differences
@ochrons I'm surprised you write that, as JSON text needs to be escaped, unlike (presumably) Boopickle. At the very least that would lead to per-char checking, which might be cheap, but not free, and any object field will have a String name, which doesn't even exist in a binary codec.
Am I missing something?
Am I missing something?
It should be faster, since JSON de/serialization requires escaping, which Boopickle, being binary, presumably does not.