vantage-vista 0.6.26

Universal, schema-bearing data handle for the Vantage data framework
Documentation
//! Rhai scripting surface over the type-erased [`Vista`](crate::vista::Vista).
//!
//! vantage-vista owns the *backend-agnostic* Rhai vocabulary, as
//! [`vantage_rhai::Vocab`] impls a host assembles, in two layers:
//!
//! - [`conventional`] — the chainable query *builder*: `table(name)` resolves a
//!   fresh target through an injected [`TargetResolver`], and builder verbs
//!   (`add_condition_eq`, `add_order`, `get_ref`…) narrow it in place. Backends
//!   layer vendor-specific verbs on top via
//!   [`TableShell::register_rhai_extensions`](crate::TableShell::register_rhai_extensions).
//! - [`fetch`] — the read-only *terminal* verbs (`list`, `get_some`, `count`,
//!   `capabilities`, `columns`, `references`) that actually read data, plus the
//!   [`runtime::run_script`] runner that drives their async fetches from
//!   synchronous Rhai.
//!
//! [`runtime::preview_script`] is the third combination: the builder layer with
//! *no* terminal verbs, rendering the query a script built instead of running
//! it. An engine that cannot fetch is a stronger guarantee than an engine that
//! merely isn't asked to.
//!
//! [`convert`] and [`introspect`] are shared internals (value round-tripping and
//! schema/capability map building).

mod conventional;
mod convert;
mod fetch;
mod introspect;
mod runtime;

pub use conventional::{
    AugmentSourceFn, ConventionalVocab, LazyValueFn, RhaiVista, ShellVocab, TargetResolver,
    augment_source_closure, eval_augment_source, eval_lazy_expression, eval_modify_script,
    eval_ref_script, lazy_value_closure, register_conventional_onto,
};
pub use convert::{
    cbor_to_dynamic, dynamic_to_cbor, map_to_record, record_to_dynamic, record_to_map,
};
pub use fetch::{FetchVerbs, register_fetch_verbs};
pub use runtime::{DEFAULT_LIMIT, MAX_LIMIT, MIN_LIMIT, preview_script, run_script};