Daniel Vigovszky comments

Results 131 comments of


                                            Daniel Vigovszky

Exclude params and cons from the derivation based on annotations

@adamw so you suggest to have a built-in `@deriveTransient` (or whatever) annotation for this. I think that would work and probably the simplest approach. Two things come to my mind:...

Exclude params and cons from the derivation based on annotations

One more thing came to my mind. If there is a global magnolia-defined transient annotation that would shortcut all derivations regardless of the typeclass which may not be a good...

Exclude params and cons from the derivation based on annotations

Ah I was thinking about both Scala 2 and 3, because I think @deusaquilus 's use case is for Scala 2 for now. @adamw thinking about the macro to decide...

Exclude params and cons from the derivation based on annotations

No I was just thinking it through better and realized that would not be possible. (At least I don't see how)

Exclude params and cons from the derivation based on annotations

I think the discussion is not really about whether to use annotations or not, but rather how configurable this behavior is. And probably also about which version (Scala 3 or...

Test fails in ZIO test runner but pass with `sbt test` or regular Intellij app runner

Similar case: https://github.com/zio/zio/issues/4896

issue_685 Client default User Agent request header

@rajcspsg could you sign the Contributor License Agreement?

issue_685 Client default User Agent request header

thanks!

issue_685 Client default User Agent request header

Merging this because the concerns seems to be solved and the client interface is being redesigned in another PR anyway.

Backward compatible variant for migration from Scala 2.12 to 2.13

I fully agree and will add some tests!