Forte Scarlet

亟待解决的其他问题： - [ ] 也许需要考虑将标准组件全部合并为统一项目共同维护？_合久必分，分久必合_。 - [ ] 需要重新考虑内部送信拦截和通知的形式。拦截不应该是事件的形式， #1016 的决定与实现的过于草率。 - [ ] 为所有组件的API考虑更好且更优的方案。在可以控制复杂度的情况下，将它们的抽象设计的更有包容性。 - [ ] 重新考虑 #1047 的实施方案与必要性，结合 #1016 一起。 - [ ] #1119

kotlinx-io 你再不 1.0 我可就不管你了 👿

Wait for the results of #102 first.

尝试手动添加 `kotlinx-coroutines-core-jvm:1.8.1` 或以上版本依赖并确保**运行时版本**正确，例如刷新、清理maven的缓存或构件产物、通过 `mvn dependency:tree` 等方式查看实际被使用的依赖版本等。

Yeah, I can understand the whole thing about overloading for explosions and everyone understanding the default behavior differently, and I recognize that. Just one problem with what was mentioned above...

> The `idOnlyAsReference` is default to false, however, one-to-many saving will modify the back-reference automatically, so the object is not id only actually. > > It may be a bug...

The temporary workaround still seems effective: you can try adding the `kotlinx-serialization-protobuf` dependency in `buildSrc/build.gradle.kts` to ensure consistent serialization versions across the build environment. ```diff // the `buildSrc/build.gradle.kts` dependencies {...

Looking forward to the resolution of this issue! A while back I tried to write a program to handle files for a friend using K/N+ktxio and was dismayed to find...

https://github.com/mamoe/mirai/issues/2570 需要等待mirai的更新

Under the conditions of kt 2.2.20 + plugin 2.2.20--0.13.1, I conducted testing using the following simple code: ```Kotlin @file:OptIn(ExperimentalJsExport::class) import love.forte.plugin.suspendtrans.annotation.JsPromise @JsExport class DBEvent @OptIn(ExperimentalJsExport::class) @JsExport data class Event( val...