@domorium/validator 1.2.0 → 1.3.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 +28 -0
- package/dist/index.cjs.js +2 -2
- package/dist/index.esm.js +529 -436
- package/dist/validator/date-v7.d.ts +8 -0
- package/dist/validator/rule-node.d.ts +2 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,34 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to `@domorium/validator` are documented here.
|
|
4
4
|
|
|
5
|
+
## 1.3.0 - 2026-08-08
|
|
6
|
+
|
|
7
|
+
- Read GEDCOM 7 dates against the calendar they name. `JULIAN 1401`,
|
|
8
|
+
`HEBREW 1 TSH 5761`, `FRENCH_R 2 VEND 8` and even `GREGORIAN 1 JAN 2000` were
|
|
9
|
+
all reported as invalid, because only v5.5.1's `@#D…@` escape was understood.
|
|
10
|
+
Each calendar's own months and epochs now apply, so `HEBREW 1 JAN 5761` is
|
|
11
|
+
refused and `BCE` is confined to the two calendars that permit it. A calendar
|
|
12
|
+
binds to the date after it, so `FROM JULIAN 1670 TO GREGORIAN 1800` is two
|
|
13
|
+
dates in two calendars.
|
|
14
|
+
- **Three v5.5.1 date forms are now refused inside a 7.0 document**, which may
|
|
15
|
+
make a file that was quiet noisy: the `@#D…@` calendar escape, a slashed year
|
|
16
|
+
such as `1 JAN 1857/58`, and the `INT 1950 (around 1950)` and `(unknown)`
|
|
17
|
+
phrase forms. Version 7.0 removed all three; a date phrase belongs in a
|
|
18
|
+
`PHRASE` substructure. GEDCOM 5.5.1 documents keep them.
|
|
19
|
+
- Stop reporting a payload the specification allows to be omitted. A payload may
|
|
20
|
+
be left out whenever its data type admits the empty string, which covers 61 of
|
|
21
|
+
the 182 payload types — `1 EVEN` with only a `TYPE` beneath it was being
|
|
22
|
+
flagged. `AGE`, `DateValue` and `DatePeriod` have their own explicit
|
|
23
|
+
permission: omitting the payload and giving a `PHRASE` instead is the
|
|
24
|
+
specification's own way to record that something happened but not what.
|
|
25
|
+
- Accept a leading UTF-8 byte order mark instead of reporting it as an
|
|
26
|
+
unexpected character. This was invisible in a browser, which strips the mark
|
|
27
|
+
while decoding, and affected anyone reading a file from disk.
|
|
28
|
+
- Say what belongs in a pointer slot. `Value for SOUR should be POINTER` named
|
|
29
|
+
the rule rather than the problem; a payload that is not a pointer at all now
|
|
30
|
+
reads `should be a pointer to a SOUR record, written as "@xref@"`, while an
|
|
31
|
+
xref that resolves to nothing names the records it could have meant.
|
|
32
|
+
|
|
5
33
|
## 1.2.0 - 2026-08-07
|
|
6
34
|
|
|
7
35
|
- Keep the spaces that belong to a value. The lexer treated the delimiter after
|