ProjectValidator
Defined in: packages/project-schema/src/validate.ts:839
Constructors
Section titled “Constructors”Constructor
Section titled “Constructor”new ProjectValidator(
options):ProjectValidator
Defined in: packages/project-schema/src/validate.ts:843
Parameters
Section titled “Parameters”options
Section titled “options”Returns
Section titled “Returns”ProjectValidator
Methods
Section titled “Methods”validate()
Section titled “validate()”validate(
value):Result<ProjectValidationSuccess>
Defined in: packages/project-schema/src/validate.ts:866
Parameters
Section titled “Parameters”unknown
Returns
Section titled “Returns”Result<ProjectValidationSuccess>
validateAdmitted()
Section titled “validateAdmitted()”validateAdmitted(
value):Result<ProjectValidationSuccess>
Defined in: packages/project-schema/src/validate.ts:892
Validates a document that is already an owned JSON snapshot, skipping the cloning admission pass in favour of assertAdmittedProjectInput.
Use this only where provenance is known — a transaction commit built from a previously admitted snapshot, for example. Every externally supplied value folded into such a document must have passed snapshotProjectInput on its own first. Anything crossing a trust boundary (load, import, restore) must keep using ProjectValidator.validate.
Legacy identity migration is not applied: $schema and schemaVersion are
root fields that no entity-scoped edit can reach.
Parameters
Section titled “Parameters”unknown