checkAsset ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

Function · import { checkAsset } from '@holostep-configurators/runtime-client'; · stable · since 2.0.0 · section 22. Pure helpers (root of the package; run in Node and the fake)

The shared check(): the server stampers, Asset Library QA, the Blender helper and the runtime run this one function. Sync, pure. Each failure is an Issue whose code names the check ('element', 'part', 'slot', 'connector', 'animation', 'connector-name-collision' or 'connector-id'); the function writes message and docs itself, so every caller reports the same words. Whatever the contract, two connectors whose authored names clean to the same name fail, and so does a connector id that contains ':' (spec section 6.9, ID1).

Declaration ​

ts
export declare function checkAsset(manifest: AssetManifest, contract: AssetContract): {
  readonly ok: boolean;
  readonly failures: readonly Issue[];
  readonly errors?: readonly Issue[];
};

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: checkAsset names no product
2. A precedent not recorded: no ledger row (coverage.json) names this member or its owner
3. Two apps, or labs not recorded: no ledger row names this member or its owner
4. The cheaper fix first not recorded per member (Appendix B decides it per need)