Collection.part ​

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.

Method of Collection · stable · since 2.0.0 · called as session.collection(name, options).part

ts
part(key: string): Part<C>;

The part for an item key; exists: false when there is none. Sync. While it doesn't exist, a write through it does nothing and records 'handle-disposed' (Part.exists): for an item a pending set() or load() will create, write through find({ collection, key }), a rule that stays pending until the item lands.

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: part 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)