Skip to content

Releases: Data-swift/ManagedModels

Objectable

01 Nov 14:51
4c4769f
Compare
Choose a tag to compare

This release marks properties as @objc if they are known to be convertible to Objective-C. This should help with/ issue #36.

The feature is quite restricted, so the user may sometimes need to add @objc himself if the macro can't detect it. It will for common base types and if properties are marked as relationships.

This version also compiles w/ SwiftSyntax 600.

Merge no more

27 Jun 13:05
82baf85
Compare
Choose a tag to compare

Some model de-duplication if the same model is specified in multiple places.

Initially

26 Jun 13:31
740e869
Compare
Choose a tag to compare

Add a new SwiftData ModelConfiguration initializer that takes PersistentModel types (and creates the schema from that).

Fixed and Xcode 16 warning for reactive conformance.

Optionally

10 May 12:26
f48cedd
Compare
Choose a tag to compare

This release fixes optional, Codable, properties as filed in issue #32.

Thanks go to @admkopec for providing the fix as well! 👍

Strictly Concurrent

24 Mar 12:45
9bfced6
Compare
Choose a tag to compare

Adds and enables strict concurrency checks on Xcode 15.3/Swift 5.10. Thanks to @radianttap!

Codable Lost

09 Feb 14:08
2ebc35a
Compare
Choose a tag to compare

This release should fix two issues resulting in #27. I.e. the transformer implementation for Codable attribute types.

NoNamed

30 Jan 17:06
cc4ba2b
Compare
Choose a tag to compare

Works w/ Xcode 15.2 again, thanks a lot Adam Kopeć!

Documentary

10 Oct 14:38
2955475
Compare
Choose a tag to compare

Added some DocC documentation.

Optionally

07 Oct 13:30
40e531d
Compare
Choose a tag to compare

Fixes Issue #22, in which optionals sometimes do not work right. Should be fine now.

MOMs

07 Oct 12:36
1530d28
Compare
Choose a tag to compare

Fixes Issue #20, the persistent model types do not generate a cached entity anymore. Multiple ManagedObjectModels can be built from a single type and the deprecated init's for that are available again.
MOMs themselves are still cached for other methods that take PersistentModel types (like .modelContainer(for: Item.self)).

Also, the attributeValueClassName of NSAttributeDescriptions isn't filled anymore w/ the corresponding Foundation types. That produced issues w/ optional attributes (NSNull not matching the set type) and doesn't seem to be required either.