@domorium/validator 1.5.0 → 1.7.0

package/CHANGELOG.md

@@ -2,6 +2,52 @@
 
 All notable changes to `@domorium/validator` are documented here.
 
+## 1.7.0 - 2026-08-13
+
+- **A date payload offers completions, and they depend on where the cursor is.**
+  Typing one got no help at all, in a format where the help is most needed. The
+  start of a value offers the calendars, the modifiers and the months; after a
+  number, the months it could still take and the epoch it could already be;
+  after `BET`'s first date, `AND`; after `FROM`'s, `TO`. An exact date is offered
+  months alone, since its grammar admits no calendar and no epoch.
+- **The months offered are the ones the calendar in force actually has.**
+  a cursor after `HEBREW 1` offers `TSH` through `ELL`, one after `FRENCH_R`
+  offers `VEND` through `COMP`, and the twelve a user knows by heart are not among them. This is the
+  case the feature is for.
+- GEDCOM 7 only. 5.5.1 keeps its months in a regular expression and its
+  `calendar` section is empty, so there is nothing there to offer from.
+
+- **A date naming a day the calendar does not have is reported.** `31 FEB 1900`,
+  `31 APR 1880`, `0 JAN` and `99 JAN` were all accepted: the grammar gives a day
+  as one or two digits, and nothing looked at the month it belongs to. Each now
+  carries `VAL014` saying which day was named and how many the month has. So does
+  `29 FEB 1900` — a year divisible by 100 and not by 400 has no 29th — while
+  `29 FEB 2000` and `29 FEB 2024` stay quiet.
+- The check is separate from the grammar and reported with a code of its own,
+  because `31 FEB 1900` _is_ a date: telling its author it is not one would say
+  the wrong thing about a value they can see is a date.
+- **A Julian date is judged by the Julian rule**, which keeps every fourth year
+  leap with no exception for centuries, so `JULIAN 29 FEB 1700` is accepted where
+  the same day in the Gregorian calendar is not. `HEBREW` and `FRENCH_R` have
+  months of their own and are not judged by anyone else's calendar. Both dialects
+  are covered, including 5.5.1's `@#DJULIAN@` escape.
+- A phrase is removed before a value is read as a date, so
+  `INT 1900 (born 31 FEB by the old reckoning)` reports nothing.
+
+## 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

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/completion/dateSlot.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Which part of a date the cursor is in. A flat list would be worse than
+ * nothing here: the months worth offering depend on the calendar named a few
+ * tokens earlier, and the keywords depend on what the value opened with.
+ */
+export type DateGrammar = "value" | "period" | "exact";
+export interface DateSlot {
+    /** A calendar may be named here. */
+    calendars: boolean;
+    /** Whose months may be named here, or null where none may. */
+    months: string | null;
+    /** Whose epochs may be named here, or null where none may. */
+    epochs: string | null;
+    /** Bare words the grammar allows here. */
+    keywords: string[];
+}
+export declare function dateSlot(typed: string, grammar: DateGrammar): DateSlot;

package/dist/document/gedcomDocument.d.ts

@@ -3,6 +3,12 @@ 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[]>;
@@ -13,7 +19,8 @@ export declare class GedcomDocument {
     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;