EmbeddedObject

A publisher that emits Void each time the object changes.

Despite the name, this actually emits after the embedded object has changed.

Creates an unmanaged instance of a Realm object.

The value argument is used to populate the object. It can be a key-value coding compliant object, an array or dictionary returned from the methods in NSJSONSerialization, or an Array containing one element for each managed property. An exception will be thrown if any required properties are not present and those properties were not defined with default values.

When passing in an Array as the value argument, all properties must be present, valid and in the same order as the properties defined in the model.

An unmanaged embedded object can be added to a Realm by assigning it to a property of a managed object or by adding it to a managed List.

The Realm which manages the object, or nil if the object is unmanaged.

The object schema which lists the managed properties for the object.

Indicates if the object can no longer be accessed because it is now invalid.

An object can no longer be accessed if the object has been deleted from the Realm that manages it, or if invalidate() is called on that Realm.

A human-readable description of the object.

Override this method to specify the names of properties to ignore. These properties will not be managed by the Realm that manages the object.

Override this method to specify a map of public-private property names. This will set a different persisted property name on the Realm, and allows using the public name for any operation with the property. (Ex: Queries, Sorting, …). This very helpful if you need to map property names from your Device Sync JSON schema to local property names.

class Person: EmbeddedObject {
    @Persisted var firstName: String
    @Persisted var birthDate: Date
    @Persisted var age: Int

    override class public func propertiesMapping() -> [String : String] {
        ["firstName": "first_name",
         "birthDate": "birth_date"]
    }
}

Returns or sets the value of the property with the given name.

Registers a block to be called each time the object changes.

The block will be asynchronously called after each write transaction which deletes the object or modifies any of the managed properties of the object, including self-assignments that set a property to its existing value.

For write transactions performed on different threads or in different processes, the block will be called when the managing Realm is (auto)refreshed to a version including the changes, while for local write transactions it will be called at some point in the future after the write transaction is committed.

Notifications are delivered via the standard run loop, and so can’t be delivered while the run loop is blocked by other activity. When notifications can’t be delivered instantly, multiple notifications may be coalesced into a single notification.

Unlike with List and Results, there is no “initial” callback made after you add a new notification block.

Only objects which are managed by a Realm can be observed in this way. You must retain the returned token for as long as you want updates to be sent to the block. To stop receiving updates, call invalidate() on the token.

It is safe to capture a strong reference to the observed object within the callback block. There is no retain cycle due to that the callback is retained by the returned token and not by the object itself.

Registers a block to be called each time the object changes.

The block will be asynchronously called on the given actor’s executor after each write transaction which deletes the object or modifies any of the managed properties of the object, including self-assignments that set a property to its existing value. The block is passed a copy of the object isolated to the requested actor which can be safely used on that actor along with information about what changed.

For write transactions performed on different threads or in different processes, the block will be called when the managing Realm is (auto)refreshed to a version including the changes, while for local write transactions it will be called at some point in the future after the write transaction is committed.

Only objects which are managed by a Realm can be observed in this way. You must retain the returned token for as long as you want updates to be sent to the block. To stop receiving updates, call invalidate() on the token.

By default, only direct changes to the object’s properties will produce notifications, and not changes to linked objects. Note that this is different from collection change notifications. If a non-nil, non-empty keypath array is passed in, only changes to the properties identified by those keypaths will produce change notifications. The keypaths may traverse link properties to receive information about changes to linked objects.

Registers a block to be called each time the object changes.

The block will be asynchronously called on the given actor’s executor after each write transaction which deletes the object or modifies any of the managed properties of the object, including self-assignments that set a property to its existing value. The block is passed a copy of the object isolated to the requested actor which can be safely used on that actor along with information about what changed.

For write transactions performed on different threads or in different processes, the block will be called when the managing Realm is (auto)refreshed to a version including the changes, while for local write transactions it will be called at some point in the future after the write transaction is committed.

Only objects which are managed by a Realm can be observed in this way. You must retain the returned token for as long as you want updates to be sent to the block. To stop receiving updates, call invalidate() on the token.

By default, only direct changes to the object’s properties will produce notifications, and not changes to linked objects. Note that this is different from collection change notifications. If a non-nil, non-empty keypath array is passed in, only changes to the properties identified by those keypaths will produce change notifications. The keypaths may traverse link properties to receive information about changes to linked objects.

Returns whether two Realm objects are the same.

Objects are considered the same if and only if they are both managed by the same Realm and point to the same underlying object in the database.

Indicates if this object is frozen.

Returns a frozen (immutable) snapshot of this object.

The frozen copy is an immutable object which contains the same data as this object currently contains, but will not update when writes are made to the containing Realm. Unlike live objects, frozen objects can be accessed from any thread.

Returns a live (mutable) reference of this object.

This method creates a managed accessor to a live copy of the same frozen object. Will return self if called on an already live object.