@domorium/validator 1.7.0 → 1.8.0
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 +15 -0
- package/dist/index.cjs.js +2 -2
- package/dist/index.esm.js +72 -49
- 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,21 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `@domorium/validator` are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.8.0 - 2026-08-14
|
|
6
|
+
|
|
7
|
+
- **A header naming a system before `GEDC` is Personal Ancestral File, and is no
|
|
8
|
+
longer judged by a specification that does not apply to it.** FamilySearch's
|
|
9
|
+
version-detection algorithm reads until whichever of `1 GEDC` and `1 SYST`
|
|
10
|
+
comes first; `1 SYST` skips the version entirely and sends the file to the PAF
|
|
11
|
+
specification. We read the `VERS` line regardless, resolved 5.5.1 and reported
|
|
12
|
+
five diagnostics from a schema the algorithm says is not the file's.
|
|
13
|
+
- `VAL015` says so and nothing else is reported, the way an unsupported version
|
|
14
|
+
already behaves. `getVersionResolution()` gains a `paf` kind carrying the
|
|
15
|
+
system the header named. Writing a PAF schema is not in scope; saying plainly
|
|
16
|
+
that this dialect is not judged here is.
|
|
17
|
+
- A `1 SYST` **after** `1 GEDC` changes nothing, which is what the algorithm
|
|
18
|
+
says: whichever comes first decides.
|
|
19
|
+
|
|
5
20
|
## 1.7.0 - 2026-08-13
|
|
6
21
|
|
|
7
22
|
- **A date payload offers completions, and they depend on where the cursor is.**
|