How did you get the snapshot version? I tried to no avail...

I maintain a fork as my feature was rejected but official snapshots are available https://oss.sonatype.org/content/repositories/snapshots/com/squareup/moshi/moshi-kotlin/1.13.0-SNAPSHOT/

sqldelight 1.x api page is 404ing https://cashapp.github.io/sqldelight/1.x/android-driver/index.md

Is this the place to request merging of https://github.com/square/javapoet/pull/840? 🙂 Please have merci on Java (records).

I'm having a strange error with Moshi last snapshot and Kotlin 1.6 / KSP in R8 release.

Error: interface qd.n is not a JsonQualifier.

(Never had an issue before. When checking bytecode after R8 retrace it gives:

.class public interface abstract annotation Lx/android/jsonapi/JsonErrorHandlingFactory$IgnoreInvalidObject;
.super Ljava/lang/Object;
.source "JsonErrorHandlingFactory.kt"

# interfaces
.implements Ljava/lang/annotation/Annotation;


# annotations
.annotation system Ldalvik/annotation/EnclosingClass;
    value = Lx/android/jsonapi/JsonErrorHandlingFactory;
.end annotation

.annotation system Ldalvik/annotation/InnerClass;
    accessFlags = 0x2609
    name = "IgnoreInvalidObject"
.end annotation

.annotation runtime Lcom/squareup/moshi/JsonQualifier;
.end annotation

.annotation runtime Ljava/lang/annotation/Retention;
    value = .enum Ljava/lang/annotation/RetentionPolicy;->RUNTIME:Ljava/lang/annotation/RetentionPolicy;
.end annotation

Source:

@Retention(AnnotationRetention.RUNTIME)
    @JsonQualifier
    annotation class IgnoreInvalidObject

So it seems the annotation is here and correct. Is there something I'm missing or some new rules that should be applied?

Anyone else having issues with moshi when trying to upgrade to kotlin 1.6.0

Could not parse metadata!

Oh no. That dance again? 🙂 We had so much pain due to having to wait/upgrade all deps with annotation processing when 1.4 came out. Kotlin guys should do backwards compatible metadata or something.

Since SQLDelight is talked about 2.0 any chance to open discussion again about an official way to build raw queries? One of the feature or my app is smart filters, where the user can virtually create any kind of filter he wants any times he wants. It would be nice to be able to support that will all the benefits like flows and all that SQLDelight propose.

You can use the driver:

driver.execute("")

From docs it's js only no ?

its not 🙂

From code too exec is JS only there's execute and executeQuery for Android driver

https://github.com/cashapp/sqldelight/blob/2b13872baef738b8f196557e68eb9885703029d7/runtime/src/commonMain/kotlin/com/squareup/sqldelight/db/SqlDriver.kt#L24

execute

executes the raw query, but does not return a

SQLCursor

,

executeQuery

does.

Ok so yes not exec but then no way to benefits and no mapping of asFlow() for example. I'll try to dig more on what trigger the requery to see if there's ways to intercept that and wrap something up.

Can the same dependency used for other native platforms for sqldelight driver be used for linux as well? I checked the repo there was a PR that was merged for adding linuxX64 as target but the readme in the github repo still doesn’t mention linux as a supported target (PFA) so I got confused here.

Linux is a native platform

Hello guys!, Are there any plans to work out hmpp in okio? I have some issues with proper resolution of

FileSystem.SYSTEM

and if I understand correctly there's a long-hanging PR by Sebastian Sellmair which could help.

No jokes about renaming this to #blocklibraries yet?

Thankfully it produces nothing so we don't have to worry

We are big enough that we could make a Cash channel, but the lines are so blurred I don't think there's a point. Might as well keep our information silo in one place for now.

#squaremonosilo

Would be cool, if someone has an idea...

in sqldelight do we have a good way of knowing the current schema version

Database.Schema.version

Where Database is your generated database

that would show if we are on a schema before migration?

Like in the https://cashapp.github.io/sqldelight/jvm_sqlite/migrations/ docs it just has "0" as old version

Ah you are using the jvm driver

You need to keep track of versions yourself in that case

multiplatform actually 😕