<@U2VU05RC4> <@U0B8FU678> re “JsonFeature automati...
# ktoro
orangy
11/09/2018, 9:40 AM
@russhwolf @mp re “JsonFeature automatically grabs a default serializer based on what gradle includes you have.” – can you elaborate on what is the problem? AFAIK it works this way only when you tell it to work like this, i.e. using
defaultSerializerm
mp
11/09/2018, 12:43 PMAs long as it's only when you opt in to "scan my classpath and use whatever", I'm OK with that. Still not sure why anyone would want that but hey 😉
r
russhwolf
11/09/2018, 3:01 PMI'm just used to configuration being a lot more explicit on the code side rather than the buildscript side. I'm used to a style like Retrofit/OkHttp, where there's similarly a lot of little configuration dependencies (such as Gson, Moshi, etc serializers, and RxJava, Couroutine, etc adapters) but you still have to tell your code which one to use after including it. In the end, it's largely a style thing and nothing prevents me from keeping my configuration explicit even when I don't need to, so it's probably not a huge problem.