Mihaela Mihaljevic
bf2dc4ece7
The validation module already implemented the composable-rule idiom under its own names (Check/Issue/SubjectContext) and a value-type Validator with duplicated traversal machinery per layer. Renamed the core types to the canonical names (Validation/ValidationError/ValidationErrorCollection/ ValidationContext/BuiltinValidation/AnyValidation), converted Validator to a reference-type class with the two-tier default-rule split, and genericized it over both Subject and Document via a new Traversable protocol so the model and tagged layers share one walk engine instead of two copies. Wired the JSON-representability rule set into the same shape and closed the two missing pieces (unwrap combinator, JSON coverage/config-pin tests).
22 lines
840 B
Swift
22 lines
840 B
Swift
public extension PureYAML.Validation {
|
|
/// The read-only bundle a type-directed check receives: the whole `document` (for cross-cutting
|
|
/// checks), the current `subject` of the check's type, and the `path` to where it sits. `Document`
|
|
/// is the type of the validated tree's root, so each layer carries a truthful document: `Model.Value`
|
|
/// for the model tree, `Tagged.Node` for the tagged tree.
|
|
struct ValidationContext<Subject: Validatable, Document: Sendable>: Sendable {
|
|
public var document: Document
|
|
public var subject: Subject
|
|
public var path: Path
|
|
|
|
public init(
|
|
document: Document,
|
|
subject: Subject,
|
|
path: Path,
|
|
) {
|
|
self.document = document
|
|
self.subject = subject
|
|
self.path = path
|
|
}
|
|
}
|
|
}
|