UpdateDataEventSchema
Writes values into data sources. Runs on the IO dispatcher.
Updates are grouped by data source and each Update resolves to a set of key/value entries: Incoming spreads the event's incomingData when it is a map (and contributes nothing when it is not), Inline writes a literal map, and Explicit writes a single known Update.UpdateDate.Explicit.dataId taking its value either from incomingData or from a literal.
Supported sources are the application and screen data holders (plain and segmented) and the plain and segmented local databases. Updates targeting navigation data, a tile or an inline source are silently ignored.
The data holders accept null values, so an explicit null clears the entry there. The databases do not support null yet, so entries resolving to null are skipped instead of written.
incomingData consumed: used by Incoming updates (spread when it is a map) and by Explicit updates whose value is Incoming.
Triggers fired:
OnSuccessEventTrigger— when every write completed without error. No data is passed downstream.OnFailureEventTrigger— when at least one database write failed. Fired once at the end, after all writes were attempted, with no data attached; each failure is logged.
Constructors
Types
Properties
This event's own children — each declaring, via its own trigger, which of this event's outgoing triggers runs it. null when this event declares no children.
The condition that must occur for this event to run — matched by structural equality (data class/data object equality) against whatever trigger value fired, never by any kind of subscription or listener registry.