07e1db950a
addArtifact was a stub: it returned null unconditionally (so the ViewModel's success path never fired), called a TODO() addArtifactVersion that threw mid-flow, and passed empty chatRoomId/userPublicKey — yielding a wrong event id and foreign-key violations. - Persist the MantraArtifact with the real chatRoomId and userPublicKey, plus a MarmotInnerEvent rumor (marmotGroupEventId IS NULL) that the outbound pipeline encrypts into the group, mirroring sendChatMessage. Set the inner event kind to ArtifactEvent.KIND so it matches the hashed id (it previously defaulted to ChatEvent.KIND). - Implement addArtifactVersion (was TODO) and create the initial version; add MantraArtifactVersion.fromArtifactVersionEventTemplate mirroring MantraArtifact for consistent id derivation. - Return the created inner event so the caller can detect success; wrap writes in try/catch to fail without crashing. Thread the required dialectId plus chatRoomId/userPublicKey and the visibility/license params (defaulting to private/cc) through MantraRepository and AddArtifactViewModel. The ViewModel now validates inputs up front, routes exceptions to onFailure, clears fields only on success, and uses isActionPending to block double submits. The screen passes dialectId = null with a TODO until a dialect picker exists; the flow fails gracefully in the meantime. Also fix the ArtifactVersionEvent.build phantom generic (TagArrayBuilder<ArtifactEvent> -> <ArtifactVersionEvent>) so it returns the correct EventTemplate type. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…