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: CHANGELOG.md
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,17 @@ Notable changes to the ObjectBox Swift library.
4
4
5
5
For more insights into what changed in the ObjectBox C++ core, [check the ObjectBox C changelog](https://github.com/objectbox/objectbox-c/blob/main/CHANGELOG.md).
6
6
7
-
## Next release
7
+
## 4.3.0 - 2025-05-21
8
8
9
9
- The generator supports Xcode 16 projects with buildable folders. [#94](https://github.com/objectbox/objectbox-swift/issues/94)
10
+
- External property types and names (via [MongoDB connector Data Mapping](https://sync.objectbox.io/mongodb-sync-connector/mongodb-data-mapping))
11
+
12
+
### Sync
13
+
14
+
- Add "Log Events" for important server events, which can be viewed on a new Admin page.
15
+
- Detect and ignore changes for objects that were put but were unchanged.
16
+
- The limit for message size was raised to 32 MB.
17
+
- Transactions above the message size limit now already fail on the client (to better enforce the limit).
4. Add a `ToolTestProjectN.swift` source file (replace `N` again) to the command line tool target. It should look like:
37
+
35
38
```swift
36
39
importObjectBox
37
40
@@ -47,7 +50,16 @@ Adding a test case requires the following steps:
47
50
5. If the code generator should succeed, add the generated `EntityInfo.generatedN.swift` to the `ToolTestProjectN`
48
51
command line tool target aswell (so it's verified it compiles).
49
52
50
-
The `RunToolTests.sh` script will run the code generator and pass the "Test Name"as the first parameter. It will also check the code generator output against a file named `Entity.generatedN.swift`, the model file against a `modelN.json` and such.
53
+
The `RunToolTests.sh` script will run the code generator and pass the "Test Name"as the first parameter. It will also
54
+
check the code generator output against files in the `expected` folder:
55
+
56
+
- (only if expected to fail) that generator output messages contain messages in a file named like `messages/messagesN.log`,
57
+
- the model file against a file named like `model/modelN.json`,
58
+
- the generated code against a file named like `entity-info/Entity.generatedN.swift`,
59
+
- a dump of the generator schema against a file named like `schema-dump/schemaDumpN.txt`
60
+
61
+
Note: by default a test will copy the expected model file before running the generator (to avoid UIDs from changing).
62
+
To start with a different model file, add a file like `model/modelN.before.json`.
51
63
52
64
### Command line tool target settings
53
65
For reference, all of the command line targets have these settings:
0 commit comments