MantraArtifact requires a dialectId (FK), but the add-artifact screen had no way to provide one. Let the user either reuse an existing source dialect or create a new one inline. - DatabaseMantraRepository.addDialect builds a DialectEvent, derives a MantraDialect with the real chatRoomId/userPublicKey, and persists it plus a MarmotInnerEvent rumor (kind = DialectEvent.KIND) for the outbound pipeline, mirroring addArtifact. getDialects exposes the chat room's dialects via a new MantraDialectDao query. - MantraDialect.fromDialectEventTemplate mirrors the other models for consistent id derivation; DialectEvent.build now takes name/country/ language (emitting NameTag/CountryTag/LanguageTag), and toDialectEvent's tag order matches build so the event id round-trips. Also fixes the DialectEvent.build / toDialectEvent phantom generics. - AddArtifactViewModel loads the dialects on init and its addArtifact now takes existingDialectId: reuse it when set, otherwise create a new dialect (fields required only in create mode), then create the artifact. - AddArtifactScreen shows a FilterChip row (one chip per existing dialect plus a "New dialect" chip); the name/country/language fields appear only when creating a new dialect. 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…