By using exact, we're locking type definitions to property?: Value which means we can't pass undefined as the value. This isn't normally a problem but it becomes one in tests when using effect/schema/Arbitrary because we can't undefine randomly generated values for certain optional properties (like ZPlane or ZPlaneLocalOffset).
By using
exact, we're locking type definitions toproperty?: Valuewhich means we can't passundefinedas the value. This isn't normally a problem but it becomes one in tests when usingeffect/schema/Arbitrarybecause we can't undefine randomly generated values for certain optional properties (likeZPlaneorZPlaneLocalOffset).