realm-kotlin
realm-kotlin copied to clipboard
realm
Kotlin Multiplatform and Android SDK for the Realm Mobile Database: Build Better Apps Faster.
[x] getIdentities() [ ] getProviderType() [ ] getAccessToken() [ ] getRefreshToken() [ ] getDeviceId() [x] linkCredentials(credentials)
![sync-by-unito[bot] avatar](https://avatars.githubusercontent.com/in/64202?v=4 "sync-by-unito[bot] avatar"){kind=avatar}
Add support for `EmailPasswordAuth.callResetPasswordFunction()`. This cannot be implemented until #648 is complete.
Currently, we have to pass in a class annotated with `RealmModule` which captures some or all the models that we would like to participate in the Realm scheam. This works...
Similar to Realm Java we should expose the ApiKeyAuth API: ```java interface ApiKey { val id: ObjectId val value: String? val name: String val enabled: Boolean } interface io.realm.mongodb.auth.ApiKeyAuth {...
Add support for `Credentials.customFunction(args: Document)`. This requires BSON support first: https://github.com/realm/realm-kotlin/issues/648
Currently, there is only limited support for visualizing the results of benchmark results in the `/benchmarks` module. We should make it easy to dig deeper into whatever results come out...
This issue is a meta issue for tracking and discussing the most important internal refactors we would like to do in the short-team: So far I have compiled the following...
Part of #713 (Claus - 2) Clean up internal Realm-hierarchy. MutableRealm was originally constructed as the user-facing writable realm, but with the introduction of DynamicMutableRealm we have some common stuff...
Fallout from https://github.com/realm/realm-kotlin/pull/669/files#r817459933 Instead of using an Executor with a normal thread for analytics. We should instead use a daemon thread. Even though the timeout for sending data is pretty...