Add example of creating interop between Realm Kotlin and a Java project. #42
Conversation
| var favoriteChild: Child? = null | ||
|
|
||
| // Expose method making it easier to use from Java | ||
| fun setChildren(children: ArrayList<Child>) { |
There was a problem hiding this comment.
If named set then we should probably clear the underlying list before adding children.
… both a Maven and Gradle App module as well.
|
I restructured the sample a bit and added all the needed docs. This PR should now be ready for review |
| } | ||
|
|
||
| lateinit var realm: Realm | ||
| val realmDispatchers = Executors.newFixedThreadPool(Runtime.getRuntime().availableProcessors() - 1).asCoroutineDispatcher() |
There was a problem hiding this comment.
Why not use a fixed single thread? this is only used from realm.query<Person>
| fun closeRealm() { | ||
| checkRealm() | ||
| realmScope.cancel("Closing Realm") | ||
| realmDispatchers.close() |
There was a problem hiding this comment.
shouldn't we also shutdown the realmDispatchers executor?
| val config = RealmConfiguration.Builder(schema = setOf(Person::class, Child::class)) | ||
| .name("javainterop-example.realm") | ||
| .build() | ||
| Realm.deleteRealm(config) // Cleanup any old test data |
There was a problem hiding this comment.
Minor: This might be surprising if the user re-run the same app unless documented ...
| } | ||
|
|
||
| fun writeData(person: Person): Person { | ||
| return realm.writeBlocking { |
There was a problem hiding this comment.
missing checkRealm() same for the below functions
| callback.update(event) | ||
| } | ||
| } | ||
| return CancellationToken(job) |
There was a problem hiding this comment.
You could also return Java's Closeable instead of CancellationToken
We are getting a few questions on how to do this. This sample project demonstrates one way of doing it by exposing a
RealmRepositoryfrom the Kotlin module that has a Java-friendly interface.It should probably not be merged as is and needs to be discussed.