Chimeway.RenderContextResolver behaviour (chimeway v1.2.0)

Copy Markdown View Source

Host-owned reconstruction boundary for deferred notification rendering.

Chimeway stores only a notification's stable key/version and opaque recipient reference. When a delivery is planned after the original trigger process has gone away, the configured resolver maps those safe identifiers to current host context and the notifier that owns rendering.

Summary

Types

context()

Callbacks

resolve(t, pos_integer, t)

Functions

resolve(notification_key, notification_version, recipient_ref)
validate_registry!()

Types

context()

@type context() :: %{notifier: module(), params: map(), recipient: map()}

Callbacks

resolve(t, pos_integer, t)

@callback resolve(String.t(), pos_integer(), String.t()) ::
  {:ok, context()} | {:error, atom()}

Functions

resolve(notification_key, notification_version, recipient_ref)

@spec resolve(String.t(), pos_integer(), String.t()) ::
  {:ok, context()} | {:error, atom()}

validate_registry!()