Struct TypeSchemaBuilder 

pub struct TypeSchemaBuilder { /* private fields */ }

Builder for creating type schemas fluently

Implementations

impl TypeSchemaBuilder

pub fn new(name: impl Into<String>) -> Self

Start building a new type schema

pub fn f64_field(self, name: impl Into<String>) -> Self

Add a f64 field

pub fn i64_field(self, name: impl Into<String>) -> Self

Add an i64 field

pub fn decimal_field(self, name: impl Into<String>) -> Self

Add a decimal field (stored as f64, reconstructed as Decimal on read)

pub fn bool_field(self, name: impl Into<String>) -> Self

Add a boolean field

pub fn string_field(self, name: impl Into<String>) -> Self

Add a string field

pub fn timestamp_field(self, name: impl Into<String>) -> Self

Add a timestamp field

pub fn object_field( self, name: impl Into<String>, type_name: impl Into<String>, ) -> Self

Add a nested object field

pub fn array_field( self, name: impl Into<String>, element_type: FieldType, ) -> Self

Add an array field

pub fn hashmap_field( self, name: impl Into<String>, key_type: FieldType, value_type: FieldType, ) -> Self

Add a HashMap<K, V> field. W17.3-4.1 — per audit §4.B builder parity with array_field. Slot storage points to HeapKind::HashMap; the schema-side variant carries the static K/V FieldTypes for compile-time checking (ADR-006 §2.7.5).

pub fn set_field(self, name: impl Into<String>, element_type: FieldType) -> Self

Add a Set field. W17.3-4.1 — per audit §4.B builder parity with array_field. Slot storage points to HeapKind::HashSet; the schema-side variant carries the static element FieldType for compile-time checking (ADR-006 §2.7.5).

pub fn any_field(self, name: impl Into<String>) -> Self

Add a dynamic/any field

pub fn field_with_meta( self, name: impl Into<String>, field_type: FieldType, annotations: Vec<FieldAnnotation>, ) -> Self

Add a field with annotation metadata

pub fn build(self) -> TypeSchema

Build the type schema

pub fn register(self, registry: &mut TypeSchemaRegistry) -> SchemaId

Build and register in a registry, using the registry’s per-instance schema-ID counter.

Since B1.7 this path must not consult current_registry, because DEFAULT_SCHEMA_REGISTRY is itself initialized via this builder and that would cause a recursive LazyLock init. Allocating directly from the target registry keeps bootstrap deterministic and per-registry isolated.