spray-json
spray-json copied to clipboard
spray
A lightweight, clean and simple JSON implementation in Scala
As title suggest upgrades dependencies including latest stable versions of plugins. Also means we should be good to mainline ScalaJS/Native support now that those projects have stabilised.
According to the [protobuf issue](https://github.com/protocolbuffers/protobuf/issues/2679), int64, uint64 type is serialized into string due to a Javascript precision problem. And it seems spray cannot read the string field as Long type....
To fix an issue with a custom implicits module due to `OptionFormat` being an inner class of `StandardFormats` breaking the match in `ProductFormats.productElement2Field` when custom module implicits are used: https://github.com/spray/spray-json/blob/a2b4986d17f8cc9c9080ecf46af8f69dc72be1d5/src/main/scala/spray/json/ProductFormats.scala#L46...
I want to convert a JsValue to Double. Code is here: `action.annotations.get("average_cpu").getOrElse(JsNumber(0)).convertTo[Double],` Don't care about the logic, I get a Option[JsValue] here and use getOrElse method to get JsValue type....
Release notes from JWT scala ( https://github.com/jwt-scala/jwt-scala/releases/tag/v9.0.3 ) imply that spray-json is no longer maintained. I thought it was feature complete and there was just no change anymore. Any reason...
Hey, I was thinking it would be good to have an optional (separate module), Scala 3 only, macro pickling module. It would preferably function similar to uPickle, so handle default...
This fixes https://github.com/spray/spray-json/issues/340 and also changes `ListBuffer` to `Map.newBuilder` since that seems like the more obvious way to build a `Map`.
Hi, I have following a case class: ``` case class UserResp( id: Int, firstName: Option[String] = None, lastName: Option[String] = None, email: Option[String] = None, avatar: Option[String] = None, avatarW:...
I saw another issue suggesting to reuse the 2.13 artifacts, but that's very undesirable for other libraries which depend on spray-json - it's not a good approach to compatibility. For...
