how can I represent

KClass<*>

in kotlin poet as a

TypeName

?

a parameterized type name of KClass over STAR

e.g.

KClass::class.asClassName().parameterizedBy(STAR)

Is there anything design wise blocking https://github.com/square/moshi/pull/1393? I think I'll have to rewrite my extension that add support for readOnly / writeOnly of generateAdapter for KSP but since it seems way less straightforward I'd like to be sure I do not start on wrong bases my journey on that.

Any update on kmp support for okhttp ? Is a kmp version of okio the primary blocker?

Not really, no. Okio is trivial. An entire HTTP client is not remotely trivial. If I had to guess I'd say it's two years away at the soonest.

I'd like to start with something very small, like supporting value types (headers, request, response) but not the actual implementation

That's potentially useful for sharing code even if it is incomplete

Call.Factory and all relevant types (Request, Response, HttpUrl), maybe Interceptor would enable quite a lot. Be a good milestone.

Unfortunately once you start pulling on this you want a lot of types and you run into hard problems with use of JVM APIs

I tried and failed to pull out a core set a few years ago

Hey how to request multiple retrofit api call without user experience effect?

I have a Wire question. We're attempting to use the WireConverterFactory send protobufs over REST to our backend. We're getting a content type

'application/x-protobuf' not supported

. Our backend team is only supporting

protobuf

, rather than

x-protobuf

content types. Is there any way to use this converter factory with protobuf content types?

Rewrite it with an OkHttp interceptor

Hello all 👋 I’m working with Wire which is working very well, however I’m having issue trying to serialize/serialize to/from Json from my Wire generated type. I’m using the wire-moshi-adapter lib. Each time I’m trying to serialize to Json. I’m having

Class java.lang.Class<com.squareup.wire.internal.FieldBinding> cannot access private final field long ...

error and when I’m trying to deserialize I got

java.lang.IllegalArgumentException: Wrong number of arguments; expected 0, got 11

any idea what I’m doing wrong ?

In Sqldelight we have

DELETE FROM XYZTable
WHERE id IN ?;

and on some android devices we are getting

too many SQL variables (code 1 SQLITE_ERROR[1]): , while compiling: DELETE FROM XYZTable WHERE id IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?....

Am I doing something obviously wrong?

sqlite has a hardcoded limit of 999 variables

So is this a bug on Sqldelight's side or do I have something misconfigured?

according to https://cashapp.github.io/sqldelight/android_sqlite/query_arguments/ the IN ? syntax works for Select. Is the issue using it with a DELETE?

https://www.sqlite.org/limits.html#max_variable_number "999 for SQLite versions prior to 3.32.0 (2020-05-22) or 32766 for SQLite versions after 3.32.0" so in theory the limit may be different on Android S, but I don't think there's anything preventing vendors from tweaking the number either…

oh nice, that is a big jump

@Trevor Stone you’ll have to run multiple queries by splitting your argument list if it exceeds 999 items

We don't actually need anywhere close to 999 items in reality, or is the fact that we're seeing this crash mean that on some devices we're already calling with over 999

I think so!

this may be relevant: https://github.com/cashapp/sqldelight/issues/1414#issuecomment-646939664

hmmmm interesting. I have no idea why this would be that large of a list already, but be a different bug lol, but that issue is very helpful, thank you

Kotlin makes it really easy to chunk: https://github.com/JakeWharton/SdkSearch/blob/33e4b60af539aef108d1d3193f99ae151ce14733/store/item/android-sql/src/main/java/com/jakewharton/sdksearch/store/item/SqlItemStore.kt#L28-L31

Thanks for the help, we had a different bug which was growing the argument list much much higher than expected, so this indirectly helped find a different issue. I'll implement chunking as well as better logging around this

I’m starting to look at okio as a potential replacement for my own multiplatform file management lib. How do you check if a

Path

matches a directory or a file (or nothing)?

Hmm you need to do something like

FileSystem.SYSTEM.metadataOrNull(path)?.isDirectory

I think, ok. Convoluted but I think I get the idea behind

FileSystem