NodetteHQ/PureYAML
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

build: classify the located-parse public types for coverage

Browse Source 
The located-parse port added four public Model types (LocatedValue, LocatedPair,
SourceRange, SourcePosition) that the validation-coverage gate flagged as
unclassified, blocking the push. They are positional projections and pure
position data with no validation invariant of their own: LocatedValue and
LocatedPair wrap an already-validated Model.Value, and SourceRange and
SourcePosition are data-transfer. Classify all four as excluded with reasons.
This commit is contained in:
Mihaela M 2026-06-29 12:19:17 +02:00
parent c1bb5aa8d6
commit b35e2a04f0
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
scripts/validation-coverage.tsv
View File

@ -24,6 +24,10 @@ PureYAML.Model.Value validated core YAML value; mapping-key uniqueness is a runt
PureYAML.Model.Mapping validated mapping keys must be unique within a mapping
PureYAML.Model.Pair excluded data-transfer key/value pair; no invariant beyond its components
PureYAML.Model.Key excluded closed sum type (string/sequence/mapping); illegal states unrepresentable
PureYAML.Model.LocatedValue excluded located projection of a Model.Value with source spans; the value invariant lives on the projected Model.Value
PureYAML.Model.LocatedPair excluded located key/value pair; data-transfer, no invariant beyond its components
PureYAML.Model.SourceRange excluded source span (start/end position); positional data-transfer, no invariant
PureYAML.Model.SourcePosition excluded source position (line/column); positional data-transfer, no invariant
# --- stream ---
PureYAML.Stream.Document excluded wraps a validated Model.Value plus an index; no own invariant

Can't render this file because it has a wrong number of fields in line 3.