Inner StoreClient receiving the validated requests
Optional validation options
Optional Readonlytrusted?: booleanWhether to skip re-validation of lookup responses against the shape, as narrowed by
the caller's model.
An immutable StoreClient wrapping store with input validation
Creates a validating store backed by a delegate.
Each method validates its inputs against the supplied shape before forwarding the request to
store:entrymust be an absolute IRI with no query string and no fragment; otherwise the request is rejected with a RangeErrormodelis validated as a template for lookup, within the query-complexity bounds (plain,depth,limit) of the caller's retrieval scope, and as a collection slice for createstate.id, if present, must be nested underentryfor create, and equal toentryfor update and insert; otherwise the request is rejected with a RangeErrorstateis validated as a resource with captive expansion capped at depth0, so inline captive batches are rejected; create validates it against the shape of the collected resources, and update and insert against the supplied shapeThe
trustedoption controls whether lookup responses are re-validated against the shape, as narrowed by the caller'smodel. It defaults tofalse, the safe choice for connectors whose source may deliver non-conforming data, such as a remote REST endpoint. Local stores that compute results themselves can passtrusted: trueto skip the redundant check.Validation failures surface as TraceError or RangeError rejections, in line with the unified Store error channel.