Add relative destinations to import declarations
This commit is contained in:
@@ -202,7 +202,7 @@ placement survives import-context and imported-parse errors. No limitations.
|
||||
|
||||
## Stage 3 — Accept and document the selected YAML syntax
|
||||
|
||||
Status: planned. Scope: directive parsing and first complete public behavior.
|
||||
Status: complete. Scope: directive parsing and first complete public behavior.
|
||||
|
||||
1. Parse sequence-of-strings `destination` in `parseImportDeclaration`.
|
||||
Construct literal keys, normalize with existing destination validation, and
|
||||
@@ -227,6 +227,14 @@ tests, local links, and everyday check. Done: syntax works across existing
|
||||
import-capable entry points and acquisition forms, not a silently ignored or
|
||||
root/path-only subset.
|
||||
|
||||
Evidence (2026-10-14): based on `49c0c6d908c0746a0ae49a332691c383ac3ff941`,
|
||||
using `go1.26.8 linux/amd64`. Engine import/glob/destination tests, root public
|
||||
destination and mounted-load tests, `TestLocalDocumentationLinks`, and
|
||||
`./scripts/check.sh` all passed. Coverage includes literal keys, malformed
|
||||
shapes and members with source-local coordinates, validation before optional
|
||||
missing/unmatched suppression, and ordinary-root plus mounted layered loads.
|
||||
No limitations.
|
||||
|
||||
## Stage 4 — Verify composition and effective version ownership
|
||||
|
||||
Status: planned. Scope: assembly interactions; reuse existing algorithms.
|
||||
|
||||
Reference in New Issue
Block a user