You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Allow missing values (implicit null)
* Update .expected files
* Rerun builder in example
* Update CHANGELOG
* Support default values during EJson deserialization
* Rerun builder in example
* Add tests
* Fix Decimal128 and RealmValue
* register allow super types to be specified
* Support DBRef
* Extend RealmValue serialization tests
* Accept a allowCustom argument on fromEJson
* Lookup PK dynmically using object schema, during RealmValue of RealmObject serialization
* Support deserializing RealmValue from DBKey
* Support Set
* Make SchemaObject const constructable again (unrelated to fix)
* Avoid allowCustom argument
* Update packages/realm_dart/test/serialization_test.dart
Co-authored-by: Nikola Irinchev <[email protected]>
* Update CHANGELOG.md
---------
Co-authored-by: Nikola Irinchev <[email protected]>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
### Enhancements
4
4
* Added a new parameter of type `SyncTimeoutOptions` to `AppConfiguration`. It allows users to control sync timings, such as ping/pong intervals as well various connection timeouts. (Issue [#1763](https://github.com/realm/realm-dart/issues/1763))
5
5
* Added a new parameter `cancelAsyncOperationsOnNonFatalErrors` on `Configuration.flexibleSync` that allows users to control whether non-fatal errors such as connection timeouts should be surfaced in the form of errors or if sync should try and reconnect in the background. (PR [#1764](https://github.com/realm/realm-dart/pull/1764))
6
+
* Allow nullable and other optional fields to be absent in EJson, when deserializing realm objects. (Issue [#1735](https://github.com/realm/realm-dart/issues/1735))
6
7
7
8
### Fixed
8
9
* Fixed an issue where creating a flexible sync configuration with an embedded object not referenced by any top-level object would throw a "No such table" exception with no meaningful information about the issue. Now a `RealmException` will be thrown that includes the offending object name, as well as more precise text for what the root cause of the error is. (PR [#1748](https://github.com/realm/realm-dart/pull/1748))
0 commit comments