Part.exists ​

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.

Property of Part · inherited by Query · stable · since 2.0.0 · called as session.node(nodeId).exists

ts
readonly exists: boolean;

False while the part is not loaded or once it is removed or disposed. A node() handle's writes stay rules on its address, pending while a queued scene write loads the node (Writer.node); through any other such part, writes do nothing, record 'handle-disposed' and resolve 'refused' with reason 'disposed'.

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: exists names no product
2. A precedent pass (through its owner Part): DOM Document.getElementById (row G31)
3. Two apps, or labs pass: 6 apps (ledger: app-04c2774145, app-b362a81c85, app-c1384707fc, app-f9a32142f1, app-fc306ec3dc; fleet cross-check: app-c1384707fc, app-f3598fad77, app-f9a32142f1, app-fc306ec3dc)
4. The cheaper fix first decided per need in Appendix B: rows G31 (through its owner Part) at tier stable (a member only where no rule, data, asset or app code serves the need)