Crate holochain_zome_types

Holochain Zome Types: only the types needed by Holochain application developers to use in their Zome code, and nothing more.

This crate is intentionally kept as minimal as possible, since it is typically included as a dependency in Holochain Zomes, which are distributed as chunks of Wasm. In contrast, the holochain_types crate contains more types which are used by Holochain itself.

Re-exports

pub use entry::Entry;

pub use header::Header;

pub use prelude::*;

Modules

agent_activity
bytes	represent arbitrary bytes (not serialized) e.g. totally random crypto bytes from random_bytes
call
call_remote
capability	Capability Grants and Claims
cell	A “Cell” represents a DNA/AgentId pair - a space where one dna/agent can track its source chain and service network requests / responses.
crdt
element	Defines a Element, the basic unit of Holochain data.
entry	An Entry is a unit of data in a Holochain Source Chain.
entry_def
fixt	Fixturators for zome types
header
info
init
link
metadata	Metadata types for use in wasm
migrate_agent
post_commit
prelude	Common types
query	Types for source chain queries
request	Types for requesting metadata
signal	App-defined signals
signature	Signature for authenticity of data
test_utils	Common helpers for writing tests against zome types
timestamp	Timestamp
trace	Types related to the debug host function
validate
validate_link
version	Tracking versions between the WASM host and guests and other interfaces.
warrant	Types for warrants
x_salsa20_poly1305
zome
zome_io

Macros

fixed_array_serialization	Serialization for fixed arrays is generally not available in a way that can be derived. Being able to wrap fixed size arrays is important e.g. for crypto safety etc. so this is a simple way to implement serialization so that we can send these types between the host/guest.
secure_primitive	Cryptographic secrets are fiddly at the best of times.

Enums

SecurePrimitiveError

Errors related to the secure primitive macro.

Traits

CallbackResult