@domorium/validator 1.0.0 → 1.2.0

package/CHANGELOG.md

@@ -2,6 +2,45 @@
 
 All notable changes to `@domorium/validator` are documented here.
 
+## 1.2.0 - 2026-08-07
+
+- Keep the spaces that belong to a value. The lexer treated the delimiter after
+  a tag as whitespace to skip, so a `NOTE` whose text began with spaces lost
+  them, and `CONC` continuations silently changed the text they rejoined.
+- Report a value that begins with a leading space or ends with a trailing one
+  correctly rather than validating a string the document never contained.
+- Name at most ten candidates when a payload is not in its permitted set, and
+  count the rest, joining them with `", "`. The full list is every matching
+  xref in the document, and interpolating it produced a message tens of
+  thousands of characters long with no break opportunity in it — enough to
+  stretch an editor's diagnostic tooltip past the edge of the screen.
+- `ASTNode` and `ASTToken` now carry `startOffset` and `endOffset`, and their
+  `range` is derived from those on access rather than stored. This is what makes
+  a large document affordable: a stored range costs three objects per token, and
+  that was most of the syntax tree's memory. `range` is `readonly` as a result —
+  code that assigned to it must set the offsets instead, and code in a tight loop
+  should read the offsets, because reading `range` allocates.
+- Build the syntax tree straight from the token stream instead of walking a
+  Chevrotain parse tree first, and index pointer targets once per document
+  rather than scanning every pointer for each one. Validation cost no longer
+  grows with records times nodes.
+
+## 1.1.0 - 2026-08-06
+
+- Accept application-defined extension tags (`_XXXX`) instead of reporting them
+  as unknown. Their subtrees are not validated: an extension's payload and
+  permitted substructures are defined by whoever authored it. See
+  [ADR-0008](../../docs/adr/0008-extension-tag-validation.md).
+- Read `HEAD.SCHMA` declarations, and report a GEDCOM 7 extension tag that is
+  used without one as `VAL008`. GEDCOM 5.5.1 documents, which have no SCHMA
+  structure, are unaffected.
+- Report a tag declared twice in `HEAD.SCHMA` as `VAL009`, and validate that
+  each declaration is an underscore-prefixed tag followed by an absolute URI.
+- Resolve the declared URI of an extension tag through `getLabel`, and offer
+  declared extension tags from `getCompletions`.
+- Stop offering root record tags as completions inside a subtree whose parent
+  type cannot be resolved.
+
 ## 1.0.0 - 2026-08-05
 
 - First stable release. `GedcomDocument` and the diagnostic shapes it returns are

package/dist/completion/completion.d.ts

@@ -1,6 +1,7 @@
 import type { ASTNode } from "../parser";
 import type { Position } from "../types/position";
 import { type GedcomScheme } from "../schemes/schema-types";
+import type { ExtensionContext } from "../validator/extensions";
 export interface GedcomCompletion {
     label: string;
     kind: "tag" | "enum" | "pointer";
@@ -10,6 +11,7 @@ interface CompletionContext {
     nodes: ASTNode[];
     pointers: Map<string, ASTNode[]>;
     scheme: GedcomScheme;
+    extensions: ExtensionContext;
     isGedcom7: boolean;
     position: Position;
     lineText: string;

package/dist/document/gedcomDocument.d.ts

@@ -8,6 +8,7 @@ export declare class GedcomDocument {
     xRefs: Map<string, ASTToken[]>;
     private errors;
     private scheme;
+    private extensions;
     private parseGedcom;
     createDocument(text: string): GedcomDocument;
     private validateLevels;