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 kitsune_p2p_timestamp as timestamp;
• pub use prelude::*;

Modules

• action
• agent_activity
• block
• bytes
  represent arbitrary bytes (not serialized) e.g. totally random crypto bytes from random_bytes
• call
• 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.
• chain
• clone
  Cells can be cloned to create new cells with the different properties.
• countersigning
  Countersigned entries involve preflights between many agents to build a session that is part of the entry.
• crdt
• dependencies
  Re-exported dependencies
• dna_def
  Defines DnaDef struct
• entry
  An Entry is a unit of data in a Holochain Source Chain.
• entry_def
• fixt
  Fixturators for zome types
• genesis
  Types related to the genesis process whereby a user commits their initial records and validates them to the best of their ability. Full validation may not be possible if network access is required, so they perform a “self-check” (as in “check yourself before you wreck yourself”) before joining to ensure that they can catch any problems they can before being subject to the scrutiny of their peers and facing possible rejection. For more details see holochain_integrity_types::genesis.
• hash
• info
• init
  Items related to the DNA initialization callback.
• judged
  Wrapper type to indicate some data which has a ValidationStatus associated with it.
• link
• metadata
  Metadata types for use in wasm
• migrate_agent
• op
  For more details see holochain_integrity_types::op.
• prelude
  Common types
• query
  Types for source chain queries
• rate_limit
  Types for rate limiting
• record
  Defines a Record, the basic unit of Holochain data.
• request
  Types for requesting metadata
• schedule
  Schedule functions to run outside a direct zome call.
• signal
  App-defined signals
• signature
  Signature for authenticity of data
• test_utils
  Common helpers for writing tests against zome types
• trace
  Types related to the debug host function
• validate
• version
  Tracking versions between the WASM host and guests and other interfaces.
• warrant
  Types for warrants
• x_salsa20_poly1305
• zome
  A Zome is a module of app-defined code which can be run by Holochain. A group of Zomes are composed to form a DnaDef.
• zome_io

Macros

• impl_to_sql_via_as_ref
  Helper macro for implementing ToSql, when using rusqlite as a dependency
• impl_to_sql_via_display
  Helper macro for implementing ToSql, when using rusqlite as a dependency

Enums

• Action
  Action contains variants for each type of action.
• Entry
  Structure holding the entry portion of a chain record.

Traits

• CallbackResult