@domorium/validator 1.4.0 → 1.6.0

package/CHANGELOG.md

@@ -2,6 +2,61 @@
 
 All notable changes to `@domorium/validator` are documented here.
 
+## 1.6.0 - 2026-08-12
+
+- **A fragment can be checked without being told it is not a file.** Text that is
+  part of a document rather than one of its own — a block pasted into a note, an
+  example in documentation, a selection — was judged as a whole file, so the one
+  thing certainly not the author's mistake was the first thing reported, and
+  nothing after it was read at all. `createDocument(text, { fragment: true,
+dialect })` reads the lines and goes quiet only about what the boundary caused:
+  the missing header and trailer, a pointer leaving the text, an extension tag
+  with no `HEAD.SCHMA` to declare it in. An unknown tag, a payload of the wrong
+  type and a level that cannot follow the line above are still reported.
+- `dialect` is named by the caller because a fragment carries no
+  `HEAD.GEDC.VERS`; without one there are still no rules to read it by.
+
+## 1.5.0 - 2026-08-10
+
+- **The GEDCOM version is resolved against a table by longest match, and a
+  version we hold no schema for no longer validates against the newest one.**
+  `2 VERS 4.0`, a garbage version and a document with no `VERS` line were all
+  checked against GEDCOM 7 and reported clean, because nothing they were checked
+  against applied to them. Three codes replace that silence: `VAL011` for a
+  version no schema describes, `VAL012` for a document whose version cannot be
+  read, `VAL013` for one checked against another version's schema. The first two
+  suppress every schema-derived diagnostic, while lexing, tree assembly and
+  level validation still run — a 4.0 file with a level that cannot follow the
+  line above it still says so. `5.5`, `5.5.5` and `5.5 EL` are checked against
+  the 5.5.1 schema with a warning naming the substitution; `5.6`, `5.4`, `5.3`,
+  `5.0` and `4` are not, because the difference runs the wrong way and the
+  substitution would report false errors on correct lines.
+- **A structure the specification gives no substructures accepted any child.**
+  `getRules` answered `undefined` both for a leaf and for a type it could not
+  resolve, and the permissive reading of the two won: 57 structures in GEDCOM 7
+  and 89 in 5.5.1 accepted anything at all, `TRLR` among them in 5.5.1. So
+
+      0 @S1@ SOUR
+      1 TITL Open Archieven
+      2 BOGUS whatever
+
+  reported nothing. A child of a leaf structure is now an unknown tag.
+
+- `2 VERS  5.5.1`, with more than one space after the tag, selected the GEDCOM 7
+  schema and the file came back clean. The delimiter after a tag belongs to the
+  payload, so the version is trimmed before it selects anything. Present since
+  1.2.0.
+- The inline form of a 5.5.1 multimedia link was unreachable, so `1 OBJE` with
+  `FILE` and `TITL` written beneath it reported `FILE` as an unknown tag. Both
+  shapes now resolve. One type serves both, so a pointer carrying children and an
+  inline form with only a `TITL` are accepted where the specification allows
+  neither; telling them apart needs a schema that can offer two types for one
+  tag.
+- New on `GedcomDocument`: `getVersionResolution()` returns the outcome above
+  without parsing a message, and `getDialect()` names the version whose rules
+  apply — or nothing, for a version we cannot judge. `VersionResolution` and
+  `GedcomDialect` are exported alongside them.
+
 ## 1.4.0 - 2026-08-09
 
 - Read a `HEAD.SCHMA` tag whose URI is a standard one as the structure it names.

package/README.md

@@ -25,6 +25,23 @@ const document = new GedcomDocument().createDocument(gedcomString);
 const errors = document.getErrors();
 ```
 
+## Fragments
+
+A fenced block in a note, an example in documentation, a selection: text that is
+part of a document rather than one of its own.
+
+```typescript
+const block = new GedcomDocument().createDocument(text, {
+  fragment: true,
+  dialect: "7.0",
+});
+```
+
+What goes quiet is what the boundary caused — the header and trailer, a pointer
+leaving the text, an extension tag with no `HEAD.SCHMA` to declare it in.
+Everything else is still read. `dialect` is needed because a fragment carries no
+`HEAD.GEDC.VERS`.
+
 ## Diagnostics
 
 `getErrors()` returns `GedcomError[]`:

package/dist/document/gedcomDocument.d.ts

@@ -1,21 +1,33 @@
 import { GedcomError } from "../types/errors";
 import { ASTNode, ASTToken } from "../parser";
+import { type GedcomDialect, type VersionResolution } from "../validator/versionRegistry";
 import { type GedcomCompletion } from "../completion/completion";
 import type { Position } from "../types/position";
+export interface CreateDocumentOptions {
+    /** Text that is part of a document rather than one of its own. */
+    fragment?: boolean;
+    /** A fragment carries no header, so the rules are named rather than read. */
+    dialect?: GedcomDialect;
+}
 export declare class GedcomDocument {
     private nodes;
     pointers: Map<string, ASTNode[]>;
     xRefs: Map<string, ASTToken[]>;
     private errors;
     private scheme;
+    private resolution;
+    private requiresSchmaDeclaration;
     private extensions;
     private parseGedcom;
-    createDocument(text: string): GedcomDocument;
+    createDocument(text: string, options?: CreateDocumentOptions): GedcomDocument;
+    private applyScheme;
     private validateLevels;
     getLabel(node: ASTNode): string | undefined;
     getPointerTargetTag(node: ASTNode): string | undefined;
     isRecordDeclaration(node: ASTNode): boolean;
     getVersion(): string | undefined;
+    getVersionResolution(): VersionResolution | undefined;
+    getDialect(): GedcomDialect | undefined;
     getCompletions(position: Position, lineText: string): GedcomCompletion[];
     updateDocument(_text: string, _range: Range): GedcomDocument;
     getErrors(_lang?: string): GedcomError[];