sphere-scala-libs icon indicating copy to clipboard operation
sphere-scala-libs copied to clipboard

Results 15 sphere-scala-libs issues
Sort by recently updated
recently updated
newest added

Added 3 rounding algorithms to substitute the methods used on BigDecimal

Given this sum type with a type hint field, optionally embedded in a test class: ``` @JSONTypeHintField sealed abstract class TypeHintEnum case object Varialtion1 extends TypeHintEnum case object Varialtion2 extends...

The @JSONTypeHintField and @MongoTypeHintField annotations are **only** respected on sealed traits when they are present on each variation of that type. For `sealed abstract classes` it is sufficient to only...

It can happen that the `Memoizer` blocks and never finishes on https://github.com/commercetools/sphere-scala-libs/blob/main/util/src/main/scala/Memoizer.scala#L20 while creating ´JSON´ instances. It looks to me like a concurrency issue, but I don't know how to...

in sphere-json & sphere-mongo we propose a generic derivation of typeclass instances based on scala macros & core generation. I experimented using another derivation mechanism based on [magnolia](https://github.com/propensive/magnolia): https://github.com/sphereio/sphere-scala-libs/tree/derive_with_magnolia I...

Since we have migrated to Scala 2.12, we are effectively only targetting Java 8. Java 8 introduced with the JSR 310 a new `java.time` API which has been built on...

The sphere-mongo library is depending on a mongo driver: https://github.com/sphereio/sphere-scala-libs/blob/15e62715c4ed2df89789210cf02b786f88cd343c/mongo/dependencies.sbt#L2 The drawback is that consumers of the library cannot control the version of the mongo driver they are using. We...

Using java annotations directly has no effect. One have to use the scala type aliases. Ex: ``` import io.sphere.mongo.generic.annotations.MongoKey case class Student( @MongoKey("_id") id: String ) ``` does not work....

Maybe we don't need `MongoFormat.default`. The only instance using it is ` MongoFormat[Option]` and this instance already handles the `None` case itself.

I think this is yet another macro bitten by the infamous [SI-8776](https://issues.scala-lang.org/browse/SI-8776 - discussion [here]%28https://groups.google.com/forum/#!topic/scala-user/oJP9aqs88rM%29). A potential pragmatic workaround is to shuffle classes around until it forces the compilation order...