Great blog! Can your library become Magnolia for Scala 3 or are there some fundamental problems? Having a single API for derivation that works both in S2 and S3 would be such a timer-saver in e.g. tapir, but maybe it's impossible (cc @propensive)
-
This Tweet is unavailable.
-
Ha :) Well I think magnolia is the only blocker when it comes to tapir-core being available for S3. And then, http4s & akka-http interpreters, of course ;)
@kubukoz created a proof of concept of Magnolia for Scala 3, which is available as a PR. It needs more work, but it certainly seems possible. I would be interested in taking a fresh look at it, about two weeks from now.
-
-
After looking at the PR i would agree. I will try to make it work this weekend.
-
Basically two things are missing to be able to port magnolia to Scala 3: Type Details & Parameters and read only cases Additional details here: https://github.com/propensive/magnolia/issues/246#issuecomment-735371209 … Maybe
@deusaquilus or@biboudis have some insights on how to achieve that? - Show replies
New conversation -
-
-
@propensive btw I hope you don‘t mind your role in my little taleThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Would love to see this too, Caliban is also relying on Magnolia for schema derivation
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.