You may want to look at using AtomicFile since process death/power loss (which is also just process death) can result in a partially written file.

Also could use Jetpack Datastore is the next level up with a Moshi serialization layer (that you'd have to write, but is easy)

datastore was such a pain to get setup correctly in another side project i had (i guess because of the protobuf compile time stuff?) but datastore with moshi is interesting... hmmm. i didn't know that was an option. I'll likely go with moshi +okio + AtomicFile as a nice quick solution

Well apparently i suck at okio. whats the proper way to create a directory + file?

@Throws(IOException::class)
fun writeStringToFile(path: Path, myMessage: String) {
  FileSystem.SYSTEM.createDirectories(path)

  FileSystem.SYSTEM.write(path) {
      writeUtf8(myMessage)
  }
}

Calling code

writeStringToFile("mydir/myMessage.json".toPath(), "hello, moto")

Keep getting

java.io.IOException: failed to create directory: mydir

edit: maybe cuz im on an emu 🤔

ooh. wonder if this can help https://gist.github.com/ZacSweers/0dfa1b38f23558cfd1a0a391cfab3542

Hello, I need some help with sqlDelight. I have a KMM project working on Android and iOS. Today I wanted to update to Kotlin 1.8.0. So I make all the updates needed, at first all was straight forward, until I get stuck with sqldelight generated the entities in 2 duplicate folders and producing a “Redeclaration” error when trying to compile the project. I search but don’t know where else to look. Is there someone here that had a similar problem with duplicate entities generated by sqlDelight or have an idea where could be the problem? I’m using the version 1.5.4 . I share an Image with the duplicate folder containing all the same classes. Thank in advance!

To authors of kotlinpoet: you've probably heard this a lot, but it wouldn't hurt to say it once more — having such a blast using this library, very enjoyable to use once you get familiar with the API (docs help a lot). So cool seeing boilerplate generated for you and by your command! 🙂 Also very readable. Cheers!

Does anyone know if you create a retrofit interface with a suspending function, does retrofit automatically switch context to the IO dispatcher behind the scenes?

I'm using moshi with codegen. I have a class

User

with many fields and class

CurrentUser

which should have all the fields from

User

plus some other keys. That's how I'm receiving it from the server:

CurrentUser

just has some additional fields that should be presented in json. e.g. user is

{"name":"Phil", "avatarUrl":"<https://some.url>"}

and current user is

{"name":"Phil", "avatarUrl":"<https://some.url>", "token":"lorem ipsum"}

I could've inherit, but it'd require me to repeat all of user fields. I solved it by making a custom adapter factory that reads extra properties from json and than pass it to

UserAdapter

to fill it. But it takes a lot of boilerplate code, maybe there's some built in solution for such case? I'd like to add some annotation to

user

property so codegen would write something similar for me. Or is there a way to build a general factory for such cases?

data class CurrentUser(
    val token: String,
    val user: User,
) {
    companion object {
        private const val tokenKey = "token"

        val adapterFactory = JsonAdapter.Factory { type, _, moshi ->
            if (type != CurrentUser::class.java) {
                return@Factory null
            }

            val userJsonAdapter = moshi.adapter(User::class.java)
            object : JsonAdapter<CurrentUser>() {
                override fun fromJson(reader: JsonReader): CurrentUser? {
                    val jsonValue = reader.readJsonValue()
                        ?: return null
                    if (jsonValue !is Map<*, *>) {
                        throw IllegalStateException("${this@Companion} readJsonValue is not map: $jsonValue")
                    }
                    return CurrentUser(
                        token = jsonValue[tokenKey] as? String
                            ?: throw IllegalStateException("$tokenKey not found in $jsonValue"),
                        user = userJsonAdapter.fromJsonValue(jsonValue)
                            ?: throw IllegalStateException("Failed to parse user from $jsonValue"),
                    )
                }

                override fun toJson(writer: JsonWriter, value: CurrentUser?) {
                    value?.user
                        ?.let(userJsonAdapter::toJsonValue)
                        ?.asMap()
                        ?.plus(mapOf(tokenKey to value.token))
                        ?.let(writer::jsonValue)
                }
            }
        }
    }
}

I’m trying to use the `Throwable`type through this code :

val error = TypeVariableName(
    name = "Error",
    bounds = listOf(ClassName(Throwable::class.java.packageName, Throwable::class.java.simpleName)),
)

but kotlin poet automatically add

import java.lang.Throwable

. How can I make it use

kotlin.Throwable

instead of the java one? I tried to specify it in the

ClassName

declaration but it did’t work.

You'll need to use

ClassName("kotlin", "Throwable")

this will produce

kotlin.Throwable

too,

import com.squareup.kotlinpoet.asClassName
Throwable::class.asClassName()

I am playing around with molecule on Jetpack Compose Desktop (in a multiplatform common module). I have found mentions about

AwtUiDispatcher

in the following discussion https://kotlinlang.slack.com/archives/C5HT9AL7Q/p1674874708031219?thread_ts=1674874313.350269&cid=C5HT9AL7Q Do you have any hint on existing implementation? I din’t find anything, neither in molecule nor in redwood. Even a hint how to use it directly with

Immediate

would helpful. Thank you.

Is there anything that describes what treehouse is exactly? I can see from the redwood repository that it seems to be some sort of library that allows zipline to interact with redwood, but without reading too deep into the code, it’s not quite clear exactly what it is. I don’t see any mentions of it in the README.

it's redwood, but the compose code runs in JS (and therefore can be updated while the app is running / without app store updates)

so redwood lets you target native UI toolkits with multiplatform composables by abstracting each toolkit into a design system (or just some representation of an abstract set of widgets). and then treehouse lets you run that compose code in JS and update it on-the-fly

That’s interesting. How will performance be affected? I’d imagine the process of serializing/deserializing the result is non-trivial?

it's pretty fast. because it's compose we're only sending tiny diffs. we actually thought json would be very slow and we'd have to switch to cbor or bson but it turns out json isn't really the slow part

also note that we use QuickJS's JSON and not kotlinx.serialiation Json which is a C library, so the heavy serialization isn't occurring in the interpreter

That’s interesting. I’ll have to keep an eye out for this. I see redwood’s started doing early pre-releases.

yep. just every month, basically.

Hi all. I'm running into an integration issue with Molecule together with Kotlin 1.8.0/18.10+ together with kotlinx.serialisation. Looks like this was due to the

compose plugin produces incorrect IR which serialization plugin is unable to work with

From release notes it looks like molecule uses compose compiler plugin 1.4.0 (stable), which have fixed by this but seems to be still reproducible. Anyone else running into this problem?

When using Molecule for Presenters, what DI-like strategies have people found to work best. I'm working in an environment where there aren't existing ViewModels or ViewModelFactories

can you expand more on that?

do you already have a presenter interface/class that gets called inside

launchMolecule

or something?

are you mentioning

ViewModel

because you want to retain your presenters across activity recreations?

For sure. I am using Molecule (technically a fork) to create a flow that does not drive UI. Essentially the output from the set of composables is json. Inside of each Composable I want to be able to leverage objects from the graph as needed. I mentioned ViewModels mostly because the android documentation essentially says "ViewModels are the way to do DI with compose"

Now as I was thinking about how best to type, I did think of a pretty good solution to my problem though 🙂 (but would still love others insight)

My opinion is that the Google guidance of using AAC

ViewModel

with DI/Compose is bad. The only thing keeping many of the architecture libraries going is momentum.

If you're doing anything outside of the Android/mobile world you almost certainly don't want to replicate what Google recommends for VM injection.