Release 12.2.0 · realm/realm-dotnet

12.2.0 (2024-05-22)

Added support for Migration.FindInNewRealm which is a helper that allows you to lookup the object in the post-migration Realm that corresponds to an object from the pre-migration Realm. (Issue #3600)
Added [System.Reflection.Obfuscation] on the generated RealmSchema field to improve compatibility with obfuscation tools that change field and property names of generated classes. (Issue #3574)
Added support for list and dictionaries of RealmValue (IList<RealmValue> and IDictionary<string, RealmValue>) to be contained in a RealmValue. Lists and dictionaries can contain an arbitrary number of collections themselves. It is possible to convert an existing collection to a RealmValue using the new static methods RealmValue.List and RealmValue.Dictionary or using the implicit operators if converting from common types like List, RealmValue[] or Dictionary. Finally, it is possible to obtain the contained collections by using the new conversion method AsList and AsDictionary. For example:
```
var list = new List<RealmValue> { 1, true, "stringVal" };

var rvo = realm.Write(() =>
{
    return realm.Add(new RealmValueObject { RealmValueProperty = list});
});

var retrievedList = rvo.RealmValueProperty.AsList();
```
(PR #3441)

Accessing App.CurrentUser from within a User.Changed notification would deadlock. (Core 14.7.0)
Inserting the same link to the same key in a dictionary more than once would incorrectly create multiple backlinks to the object. This did not appear to cause any crashes later, but would have affected the value returned by RealmObject.BacklinksCount and queries involving backlinks counts. (Core 14.7.0)
Fixed an issue that would cause RealmObject.DynamicApi.GetList/Set/Dictionary to fail when the collection contains primitive values. (Issue #3597)