Hello 👋 We’re upgrading to SQLDelight 1.5.3 and running into an error that I can see is resolved in 2.0.0 alpha 2. The entry in the changelog is

[Compiler] Erroneous 'Multiple columns found' error

but there’s no issue or PR linked to it I was hoping someone could point at the fix or a workaround that doesn’t involve updating to the alpha

NM, Was able to find this https://github.com/AlecStrong/sql-psi/issues/145 Using an alias as a workaround seems to do the trick

Is there a known future for Molecule: https://github.com/cashapp/molecule I think it's a really neat concept and I had fun playing with it, but I'm unsure if it's a long term project, or more of an experiment

it is critical infrastructure for Cash App

we are using it everywhere

it's also like 30 lines of code so not exactly a risky thing to use as you can pretty trivially copy it into your project if we were to abandon it (which we're not)

Wow that's good to know. Was the motivation that it is easier to train people in Compose vs Flow or was there a different driver

it's more that the programming style of Compose really shines for this use case compared to deeply-nested chains of stream operators

the README tries to motivate our use case. we have a strong layering split between presenter and UI but want to leverage the programming style of Compose

Makes sense. Once it has multiplatform support I'd try and explore it at a larger scale

My other concern is that Compose has a tight coupling with the kotlin compiler version. Maybe it is just inevitable, but decoupling language features from a specific target (android level at the time) was always such a nice benefit

Cash App is built on it so we’re gonna be using it for a looooong time

kotlin compiler plugins are going to be ABI stable in the next release (1.7.0) so I think the coupling will go away now

i'm not sure that's still true, but it would be nice

plus K2 throws a whole wrench into the equation

true 🪦

I thought the plugins ABI would only be stable for K2. If that’s the case, we may not get the stable ABI until 1.8 or 1.9

this was my guess: https://kotlinlang.slack.com/archives/CJLTWPH7S/p1653335584686879?thread_ts=1653335064.742759&cid=CJLTWPH7S

Paparazzi - I'm testing a composable with

val animatedImage = AnimatedImageVector.animatedVectorResource(R.drawable.avd_check)

that results into

java.lang.NullPointerException: res.getXml(resId) must not be null

How can I fix/mock that? Thx

Can you file an issue on github with the full stacktrace?

the latest version of Moshi , doesnt work with kotlin 1.7.0? Will there be a new versionany time soon?

Yes. Though I might ask our Moshi hero @Zac Sweers for what soon means!! (I'm happy to cut releases but Zac really runs the show)

Hey everyone 👋 I'd really love to try the latest changes in SqlDelight but I am failing to depend on the SNAPSHOT. There also has not been a new alpha release in quite some time. Can anyone point me in the right direction to consume the SNAPSHOT, or is there perhaps a new alpha on the horizon? There are a lot cool fixes made to Postgres dialect that I'd love to try out.

What problems do you have? Normally simply adding the repositories is enough, I also use the snapshots artifacts in some projects

I can do an alpha today once the suspending transaction stuff is in

feels like a good time

and released

Is there any documentation for the migration squashing?