-
There is currently no way to use the `derives` keyword to generate `Config` directly.
It is possible to do `derives DeriveConfig` but that gives you a `DeriveConfig`, not a `Config` so you still ne…
-
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](h…
yanns updated
4 years ago
-
Probably this would involve a generic module in Scala3, with its own `Generic` that allows to and fro from tuples.
The intermediate tuple elements can stay as type members, allowing us to use `Conv…
-
Hi,
I am struggling with the migration of diffx to scala3, especially with the derivation mechanism.
I did a quick check and it seems that changing the `Eq` tc from magnolia examples also doesn'…
-
Magnolia is moving quite slowly, and I think that I can implement all of it’s functionality
using Scala 3’s auto derivation + a few simple macros for case class annotations.
-
Given the following derivation:
```scala
import SchemaType.*
import magnolia1.*
import scala.deriving.Mirror
sealed trait SchemaType[T]
object SchemaType extends Derivation[SchemaType] {
…
adamw updated
2 years ago
-
When we use derivation on a user-defined case class, some type-class instances might be missing. Magnolia at the moment may only report on the first missing instance.
Is it possible to change the w…
-
I have a failing spec in my project that is coming from a null typeclass, and I suspect this is a bug in Magnolia
```
[info] - should derive a case class *** FAILED ***
[info] java.lang.NullPoi…
-
Let's talk about circe again :)
There's `semiauto` mode, which is quite handy in many cases. In this mode the deriver doesn't use itself recursively to derive underlying types. Essentially, the der…
-
https://github.com/spotify/scio/blob/master/build.sbt#L110
Scio master (since `0.8.0-beta1`) has switched to latest magnolia (`0.12.0`) for Scala 2.13 while pinging my fork `0.10.1-jto` for Scala 2…