So now we have a Play Json format for a case class with more than 22 fields, and can use it as described in https://www.playframework.com/documentation/2.5.x/ScalaJsonCombinators[Play Json documentation]
## Second approach
I don’t consider having a case class with so many fields a good solution.
A better solution is to organize these fields in “logical” embedded case classes.
[source, scala]