Struct ProvBackend 

pub struct ProvBackend { /* private fields */ }

A backend over a single prov document, editing its embedded metadata.

Implementations

impl ProvBackend

pub fn open( path: impl Into<PathBuf>, text: impl Into<String>, ) -> Result<Self, BackendError>

Open a prov document from its full text, with no schema. Errors if prov cannot parse it.

pub fn open_with_schema( path: impl Into<PathBuf>, text: impl Into<String>, schema: Schema, ) -> Result<Self, BackendError>

Open a prov document carrying the workspace schema — the prov-aware path, so the flower model validates controlled fields and offers pickers.

pub fn body(&self) -> Result<String, BackendError>

The prose body outside the metadata block — the region a leaf editor would own. Empty for a whole-file config document.

pub fn has_body(&self) -> Result<bool, BackendError>

Whether the document has an editable prose body (a fenced carrier). A whole-file config document has none — its body cannot be replaced.

pub fn set_body(&mut self, body: &str) -> Result<(), BackendError>

Replace the prose body, leaving the metadata block untouched — the write path for edits a leaf editor makes to body.

Uses fig’s Embed::replace_body (the same lossless primitive prov edits through). A frontend that wants fixity/updated restamping routes this through prov’s write path instead; here it demonstrates that the metadata and body regions edit independently over one document.

Trait Implementations

impl Backend for ProvBackend

fn apply(&mut self, op: EditOp) -> Result<(), BackendError>

Apply one edit. Atomic: on Err, the document is unchanged.

fn to_value(&self) -> Result<Value, BackendError>

The current value tree to render (for an embed backend, the metadata region — not the whole host file).

fn source(&self) -> Result<String, BackendError>

The canonical serialized form the embedder persists on save (for an embed backend, the full rendered host file).

fn schema(&self) -> Option<Schema>

The schema governing this document, if the backend knows one. The backend is exactly the component that knows where the document came from, so it is the right place to know what governs it — a prov backend returns the schema resolved from the workspace config; a standalone config file has none. Defaulted to None so existing backends are unaffected.