you can return

Response<Unit?>

and just ignore it

Hm, that's really unexpected. Why doesn't retrofit handle this?

it does handle it

it bypasses the converter and returns null

it just has poor interaction with other feature you're trying to use

Looking forward to this. Using

Unit?

as the response type didnt work as well. Also

Void

and

Void?

didnt work. I'm using

Response<Unit?>

and manual re-throw the exception, but it feels really weird using it like this. Should I open an issue for this?

No. It's already tracked.

@Paul Woitaschek Use

Call<Void?>

+

await()

in the meantime.

Is there a reason why the moshi codegen doesn't automatically create an adapter for sealed class hierachies? It's quite error prone to annotate every element by hand and then register all the subtypes

Is there a way to disable leakcanary 2.0 completed in instrumented tests? I'm looking at docs and it only provides an opt-in setting

How to handle no internet connection with retrofit2? Should I make internet connection check inside of a interceptor?

And do what instead? You're far better off assuming every call site can fail with any IOException subtype

Does SQLDelight handle bulk inserts at all?

The best approach to making SQLDelight tSQL

suspend

is to have some sort of database manager that wraps all calls in

withContext

right? Or is there something that I've missed that's better

How should I be handling concurrency within SQLDelight using the paging extension? Is

AsyncListUtil

the preferred method?

Hi! Will the following:

Okio.buffer(Okio.source(context.assets.open("countries.json"))).use {
      adapter.fromJson(it)
    }

close all intermediate closables? InputStream, source, buffer.

yes

Hi. I feel like I'm failing to understand something fairly basic about Moshi and JsonAdapters.

When I have a

Moshi

object, I can ask Moshi to create an adaptor for some random custom class, as per the README:

val moshi = Moshi.Builder().build();
    val jsonAdapter = moshi.adapter(BlackjackHand::class.java);

Also as per the README, I can build my Moshi object to have a list of custom adapters it knows about:

val moshi = Moshi.Builder()
      .add(ZonedDateTimeAdapter)
      .add(BigDecimalAdapter)
      .build()

Is it a bug that enums that are part of the path are not parsed from their

@Json

representation?

(KotlinPoet) If I create a class and then add a top level function in the same filespec that has the created class as Parameter, how can I prevent an import statement being created for the function parameter?

Does it break anything? Just sounds like a small bug

@Paul Woitaschek what path? failing test case?

The retrofit path annotation. I see if I can create a testcase

oh, Retrofit

i assumed you were referring to Moshi because of

@Json

Retrofit knows nothing about

@Json

you can register a string converter for your enum type that looks up the

@Json

annotation and returns its value