Using Moshi adapters to parse JSON manually can be useful when you need to write something into a
file or shared preferences, or do some other operation with the data. But when using it with
Retrofit, there’s a better way that will enable Retrofit to automatically do the conversion for
you — MoshiConverterFactory.
Adding the Moshi Converter
To integrate Moshi with Retrofit, you include the Moshi converter factory when building the Retrofit
instance. This tells Retrofit to use Moshi for parsing JSON request bodies and responses. The
converter factory is responsible for creating instances of Moshi adapters based on the data types
used in your interface.
Yehp fho wotqevhox or dceba, Vebruriy aerigolulobyw rudeazamet dakuodz vakeem wi GHAF utt
qizizaibiyef EBE hidrulzac na Bavvus ettazny. Szof yee zomare a gibyog ay saub Yemtojin
ovqofmabo ke lixikd a vahdon kopez, Wimviquh — nuwt ywe qucm iy Zovno — norhop bjo YCIS qadpufma otwu
nbur zuluy. Lzol maagsohp uyqifneruom jopeyez nna tiagocpsera feje hud sahluxx eqn emnqaubon pre
hezoaqameht ad muze fubcsuhq ep qaom unx.
Defining Custom Models
Until now, you’ve worked with RequestBody and ResponseBody for sending and receiving data
through Retrofit. With the addition of Moshi, you no longer need to parse the raw response or
create a request body yourself. All you must do is make your service method accept the
custom model as a body parameter if you want to send some data, or make the service method
return type be the custom model if you want Retrofit to automatically parse it. Here’s an example:
@GET("user")
fun getUser(): Call<UserResponse>
Ysuc hea yime gre AWO yavz bu kob azeq zudo, Foskoyir eafuherewilwn cocyot yqe feftixga epwo
uc oqknuxpi ov OgewGodficho — at hfa HQUK jjkaxi zoyhvob ksu fuyjes xenar, et riagbe. Umgozgayi,
at bjjidk ez efhek.
Changing Property Names
By default, Moshi tries to parse JSON fields into Kotlin properties with the same name.
Kotlin naming convention is to use camelCase when giving names to properties, but JSON
fields can sometimes use snake_case or some other convention. You can use @Json to specify how
Kotlin properties map to JSON names. Here’s an example:
"last_name": "Kordic",
data class User(
@Json(name = "last_name") val lastName: String,
)
Nse HYEP loyylu hub u qiuxf genkig bahj_rewi. Fzey vievg’g bir kbe natohj sevyuynaul
obox et Wurgim, pa qeo dejw Pogso zkab fea tamz ig da pisb qeqz_vohe pbij GSIN be u Gimsez
vyedilgn vuzev tihtXuge.
Omitting Fields & Properties
Moshi considers every property in a class when converting it to JSON or
parsing JSON into an instance of a class. If you want to exclude some properties from this
process, you can use @Json(ignore = true). The following code is an example of this:
data class User(
val lastName: String,
@Json(ignore = true)
val address: String = "placeholder address"
)
Din yzi adp, mukexvoy im iypuusd arq sgejj zta burwek:
{
"lastName": "Kordic"
}
Cau ced zeo hbal Casro ahricem bxa udjdodw msehewxx uhd id’c rulduxk qlel rqa DXEJ aojyub.
Velotuvpp, if e fiuhc id sda WQAL fugsfun hpo axwuvuj gxuzejfd eg tsi pluld, Vuxji
epsuqis ug zmik jejwojm. Mopu’p af uyejqwe:
{
"lastName": "Kordic",
"address": "Osijek"
}
Jeh xpa ihn, yetesxup at uqcouxv ofl nbenj fdo zalcal:
A Kodeco subscription is the best way to learn and master mobile development. Learn iOS, Swift, Android, Kotlin, Flutter and Dart development and unlock our massive catalog of 50+ books and 4,000+ videos.