Allow case class member names to be customized when deriving the codecs #33
Conversation
|
Hi, thanks for this work! I think that’s an interesting feature, however my main concern is that the current design to configure the derivation process is not to use implicits but usual parameters (like I will add some additional comments directly on the code. |
| } | ||
| } | ||
|
|
||
| trait Adapter extends (String => String) |
There was a problem hiding this comment.
In general I tend to avoid extending => for types populated by implicit values, because such values can act as implicit conversions.
(this behaviour should not happen here, though, because the argument and return type are the same, though)
|
Hi, no problem. Yes, the main reason I've decided to use that design was to being able to compute the field names only once. I'll try to find some time to work on the explicit configuration. |
This is to allow for case class members to be transformed, adapting to custom fields casing in the json.
For example it can be used to convert field names to snake case.
I consider it a first draft, to get some ideas around the possible solution, but it's already working and have added some tests for it.