You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the android library uses Jackson as a serialisation library. This makes Jackson a transitive dependency that lands in the consumers dependency tree.
My proposal would be to adapt a more agnostic approach and create an abstraction layer like a Converter (similar to the one in https://github.com/square/retrofit) and allow consumers to select different types of implementations via different artefacts.
There are at least 3 popular libraries used in Android development, so at lest does can be added as standalone artefacts:
Currently the android library uses Jackson as a serialisation library. This makes Jackson a transitive dependency that lands in the consumers dependency tree.
My proposal would be to adapt a more agnostic approach and create an abstraction layer like a Converter (similar to the one in https://github.com/square/retrofit) and allow consumers to select different types of implementations via different artefacts.
There are at least 3 popular libraries used in Android development, so at lest does can be added as standalone artefacts:
native-navigation-converter-gson
for Gsonnative-navigation-converter-moshi
for Moshinative-navigation-converter-jackson
forJackson.The text was updated successfully, but these errors were encountered: