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
Copy file name to clipboardExpand all lines: objectbox/CHANGELOG.md
+21Lines changed: 21 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,24 @@
1
+
## latest
2
+
3
+
This is a 1.0 release candidate - we encourage everyone to try it out and provide any last-minute feedback,
4
+
especially to new/changed APIs.
5
+
6
+
* Change the "meta-model" fields to provide completely type-safe query building.
7
+
Conditions you specify are now checked at compile time to match the queried entity.
8
+
* Make property queries fully typed, `PropertyQuery.find()` now returns the appropriate `List<...>` type without casts.
9
+
* Query `stream` and `findStream()` are replaced by `QueryBuilder.watch()`, i.e. `box.query(...).watch()`.
10
+
* Query conditions `inside()` renamed to `oneOf()`, `notIn()` and `notInList()` renamed to `notOneOf()`.
11
+
* Store `subscribe<EntityType>()` renamed to `watch()`.
12
+
* Store `subscribeAll()` replaced by a shared broadcast stream `entityChanges`.
13
+
* Entities can now contain `final` fields and they're properly stored/loaded (must be constructor params).
14
+
* Flutter desktop - native library is now downloaded automatically, same as for mobile platforms.
15
+
* Follow exception-vs-error throwing conventions - throwing errors when it's a permanent developer-caused error. Namely,
16
+
there's a new `UniqueViolationException` thrown when an object you're trying to `put()` would violate a `Unique()` index.
17
+
* Even higher than usual amount of internal optimizations and improvements.
18
+
* Update to objectbox-c v0.14.0.
19
+
* Update to objectbox-swift v1.6.0.
20
+
* Update to objectbox-android v2.9.2-RC.
21
+
1
22
## 0.14.0 (2021-04-01)
2
23
3
24
* Fix non-nullable `DateTime` fields deserialization regression (introduced in v0.13.0) - fields were read as nanosecond instead of millisecond timestamp.
0 commit comments