Erlend Hamnaberg
Erlend Hamnaberg
See this commit: https://github.com/tpolecat/doobie/commit/5a71f28a1d461e86ce9a44ddd42e46a0bb8bc61d#diff-5634c415cd8c8504fdb973a3ed092300b43c4b8fc1e184f7249eb29a55511f91
Would this be possible to revisit? Scala 3 has wonderful semiauto capabilities thanks to the `derives` keyword.
This should have been fixed in 0.21.24. Please try with that, reopen if not.
@amumurst Do you have any more information?
I dont want to have DTOs, meaning derving this automatically. I care too much about names of json properties for not having those reflected in the scala case classes directly....
We could also generate sources for scala2/scala3 accordingly, by retaining the old constraints in scala2 and having a pure tuple version in scala3.
@isomarcte did you find an alternative solution?
An attempt of doing this can be seen here: https://github.com/hamnis/dataclass-scalafix
@zarthross any way forward here? are there any users that uses ProductN instead of TupleN?
According to https://github.com/lampepfl/dotty/issues/15253#issuecomment-1135848470 this will not really improve the situation since the long term goal is to get rid of the arity based types. It will work for the short...