Structs
- This will be used to send data events as signals to the UI. All signals relating to the entry type will share this high level structure, creating consistency. The
data
field should use the variant (Create/Update/Delete) that matches the variant foraction
. So ifaction
is variant ActionType::Create thendata
should beSignalData::Create
. It serializes with camelCase style replacement of underscores in object keys.
Enums
- when sending signals, distinguish between “create”, “update”, and “delete” actions via this enum. Serializes to/from “create” | “update” | “delete”
- Distinguishes between what data structures should be passed to the UI based on different action types, like create/update/delete this will be used to send these data structures as signals to the UI When Create/Update, we will pass the actual new Entry but when doing Delete we will naturally only pass the ActionHash
Functions
- Grant unrestricted access for this agent to receive calls to its
recv_remote_signal
endpoint via others callingremote_signal