-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Core 13.2.0 #1157
Update to Core 13.2.0 #1157
Conversation
# Conflicts: # Jenkinsfile # packages/cinterop/src/androidAndroidTest/kotlin/io/realm/kotlin/test/CinteropTest.kt # packages/cinterop/src/nativeDarwinTest/kotlin/io/realm/kotlin/test/CinteropTest.kt # packages/external/core
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK to me. There are some itchy things around the schema that needs to be replicated all over the realms, but I guess cleaning it up goes better together with the standalone DynamicRealm
-API and/or rework of our internal reuse of interfaces, etc. to improve the internal Realm hierarchy implementation.
.../library-base/src/androidMain/kotlin/io/realm/kotlin/internal/platform/SystemUtilsAndroid.kt
Outdated
Show resolved
Hide resolved
@@ -519,7 +519,8 @@ class RealmModelSyntheticPropertiesGeneration(private val pluginContext: IrPlugi | |||
property.locationOf() | |||
) | |||
} | |||
val isIndexed = backingField.hasAnnotation(INDEX_ANNOTATION) | |||
// See https://github.com/realm/realm-core/issues/6187 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we didn't align on whether RealmSchema
should reflect the actual schema or whether there was an index in effect. If going with the latter then I guess it should just be fixed in core. If we wan't to mimic the return value until it is fixed in core then we shouldn't change the schema here but just pass isPrimaryKey || isIndexed
to the ValuePropertyType
constructor in https://github.com/realm/realm-kotlin/blob/main/packages/library-base/src/commonMain/kotlin/io/realm/kotlin/internal/schema/RealmPropertyImpl.kt#L47
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, right now I'm adding it here, while waiting for the Core fix, but also because I'm a little afraid that Core might not do it correctly at all, so just hacking the return value would just seem to mask even more bugs? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussion, I'll remove this fix for now and revert the test. This is now a "known bug" and we will talk with Core about a resolution.
...ages/test-base/src/androidAndroidTest/kotlin/io/realm/kotlin/test/shared/RealmSchemaTests.kt
Outdated
Show resolved
Hide resolved
packages/library-base/src/nativeIos/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Outdated
Show resolved
Hide resolved
packages/library-base/src/nativeDarwin/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Show resolved
Hide resolved
packages/library-base/src/nativeIos/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Outdated
Show resolved
Hide resolved
packages/library-base/src/nativeIos/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Outdated
Show resolved
Hide resolved
packages/library-base/src/nativeMacos/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Outdated
Show resolved
Hide resolved
packages/library-base/src/nativeMacos/kotlin/io/realm/kotlin/internal/platform/SystemUtils.kt
Outdated
Show resolved
Hide resolved
@@ -107,23 +105,34 @@ public class AppConfigurationImpl constructor( | |||
private fun initializeSyncClientConfig(): RealmSyncClientConfigurationPointer = | |||
RealmInterop.realm_sync_client_config_new() | |||
.also { syncClientConfig -> | |||
// TODO use separate logger for sync or piggyback on config's? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not really sure that I get the full details of this ... but do we need to note this in the CHANGELOG?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Only a minor thing with the changelog. ... And of course when CI is green 😅
Update to Realm Core 13.2.0
The changes to Sync Connection Parameters are defined here: https://docs.google.com/document/d/1jUeN71gzQoLoYxHUawzIQaDVD2xDLbtbWkmxjIMcN-U/edit
TODO
closeShouldFreeMemory
is failing on macOS. Turns out to only happen when running this test individually.