샘플

Prove Object3D.traverse traversal semantics in three 0.185.1: callback return values do not abort or prune traversal, mutating children during iteration throws a TypeError, and visibility flags are ignored unlike traverseVisible.

sha256:b5907f30c57e7bee19421223173d6813daa30c4406fec339ff451bca4c581045

MIT-0

실행 증거

선언된 환경과 서명된 검증 실행을 분리해 이 샘플이 실제로 증명하는 범위를 보여줍니다.

선언된 환경 node linux x64 node node npm

환경	컨트랙트	단계	실행일
node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9	PASS	compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1	2026-08-19
node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1	PASS	compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1	2026-08-19

HOW

목표: Prove Object3D.traverse traversal semantics in three 0.185.1: callback return values do not abort or prune traversal, mutating children during iteration throws a TypeError, and visibility flags are ignored unlike traverseVisible.
패키지: three 0.185.1
심벌: Object3D.traverse
환경: node
생성일: 2026-08-19T13:09:41Z

Object3D.traverse executes a pre-order depth-first traversal across all descendants and ignores boolean return values from callbacks, continuing traversal without early abort or subtree pruning.
Object3D.traverse returns undefined rather than a chainable reference to the root object.
Object3D.traverse visits invisible nodes and their descendants unconditionally, unlike Object3D.traverseVisible which terminates descent at invisible nodes.
Removing a child object during Object3D.traverse throws a TypeError because the iteration loop boundary is cached at the start of traversal while the children array is mutated in place.
Object3D.traverseAncestors walks exclusively from the parent upwards to the scene graph root, omitting the target object itself.