@domorium/validator 1.7.0 → 1.8.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +29 -0
- package/dist/index.cjs.js +2 -2
- package/dist/index.esm.js +105 -82
- package/dist/types/errors.d.ts +2 -0
- package/dist/validator/versionRegistry.d.ts +6 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,35 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `@domorium/validator` are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.8.1 - 2026-08-17
|
|
6
|
+
|
|
7
|
+
- **A note written as text in a 5.5.1 file is no longer reported.** `1 NOTE plain
|
|
8
|
+
text` was told to be a pointer to a `NOTE` record, though `NOTE_STRUCTURE` has
|
|
9
|
+
two forms and the text itself is the second. A note that ran to a `CONT` line
|
|
10
|
+
escaped, because the pointer rule stays silent for a structure with children,
|
|
11
|
+
so the report landed only on one-line notes — which every export from
|
|
12
|
+
MyHeritage, Ancestry and Gramps is full of. The schema still names the pointer
|
|
13
|
+
form, which is the one with a target to resolve and to complete.
|
|
14
|
+
- **A source citation carrying its description is no longer reported either.**
|
|
15
|
+
`1 SOUR Parish register, Warsaw, vol 3 p 41` is the branch 5.5.1 provides for
|
|
16
|
+
systems that keep no source records, and `TEXT` written beneath it is no longer
|
|
17
|
+
an unknown tag. See [ADR 0010](../../docs/adr/0010-two-form-structures-in-5-5-1.md).
|
|
18
|
+
|
|
19
|
+
## 1.8.0 - 2026-08-14
|
|
20
|
+
|
|
21
|
+
- **A header naming a system before `GEDC` is Personal Ancestral File, and is no
|
|
22
|
+
longer judged by a specification that does not apply to it.** FamilySearch's
|
|
23
|
+
version-detection algorithm reads until whichever of `1 GEDC` and `1 SYST`
|
|
24
|
+
comes first; `1 SYST` skips the version entirely and sends the file to the PAF
|
|
25
|
+
specification. We read the `VERS` line regardless, resolved 5.5.1 and reported
|
|
26
|
+
five diagnostics from a schema the algorithm says is not the file's.
|
|
27
|
+
- `VAL015` says so and nothing else is reported, the way an unsupported version
|
|
28
|
+
already behaves. `getVersionResolution()` gains a `paf` kind carrying the
|
|
29
|
+
system the header named. Writing a PAF schema is not in scope; saying plainly
|
|
30
|
+
that this dialect is not judged here is.
|
|
31
|
+
- A `1 SYST` **after** `1 GEDC` changes nothing, which is what the algorithm
|
|
32
|
+
says: whichever comes first decides.
|
|
33
|
+
|
|
5
34
|
## 1.7.0 - 2026-08-13
|
|
6
35
|
|
|
7
36
|
- **A date payload offers completions, and they depend on where the cursor is.**
|