Improve implicit resolution of validated mapping#88
Conversation
|
I think we should keep this separate. The problem is when you have multiple valid implicits, scala is not always smart enough to tell you there are too many and it cannot choose one. In the past, this led to cases where the app was using the wrong implicit. For example, if there is a circe encoder for type T and a Validated mapper for type T, which should be used? there is a mapping for json types and there is a mapping for validated so.. |
|
this PR just get's rid of |
| import SlickValidatedGeneric.validatedGenericMapper | ||
|
|
||
| case class Book(id: Long, title: String, code: Option[String] = None) | ||
| case class Book(id: Long, title: BookTitle, code: Option[String] = None) |
There was a problem hiding this comment.
It seems BookTitle is not defined?
There was a problem hiding this comment.
I pushed a new commit with the definition.
Signed-off-by: Ignacio Lucero <ignacio.lucero@here.com>
3 participants
No description provided.