data-cap
    Preparing search index...

    Function buildData

    • Declares a schema's field contract. data.fields is synchronously readable the instant this returns -- populated with declared defaults -- there is no throw-until-ready gate (a deliberate divergence from @maverickcer/env-cap's createEnv; see specs/architecture.md).

      buildData is the low-level, pure/synchronous primitive: config only ever reads fields (a getters/mutators/subscriptions section on the same object, if present, is simply ignored here -- that's what the batteries- included createData from data-cap/runtime is for). data. info is present (mandatory, never optional) but starts empty: nothing has executed yet, so there is nothing to report metadata for.

      Type Parameters

      Parameters

      Returns BuiltData<TFields>

      Throws synchronously, at call time, for a structurally invalid field default (a function value, or a cyclic reference) -- this is a schema-authoring mistake the developer must fix, not a runtime condition to warn-and-continue past.