edfcore 0.3.85 → 0.3.87

package/CHANGELOG.md

@@ -6,6 +6,37 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.3.87
+
+- **Fixed** `api-validate.md` saying "The other five are also emitted by the parser" under a
+  ten-row table from which four codes had just been excluded. Ten minus four is six, and all six
+  really are parser codes: `RECORD_SIZE_ABOVE_RECOMMENDED`, `PATIENT_ID_NONCONFORMANT`,
+  `RECORDING_ID_NONCONFORMANT`, `DATE_UNPARSEABLE`, `DATE_FIELDS_DISAGREE` and
+  `STARTTIME_UNPARSEABLE`.
+- The sentence is load-bearing — it is how a reader knows the report stands on its own rather than
+  only making sense beside `header.diagnostics` — so a reader who counted the table and got a
+  different answer had reason to doubt the claim rather than the arithmetic.
+- Both numbers are now derived from the table itself: the count of rows, minus the count the prose
+  says exist nowhere else. Adding a row fails the suite until the prose is updated, which is the
+  rule 0.3.63 applied to `diagnostics.md` after the same kind of drift.
+
+## 0.3.86
+
+- **Fixed** `formatStartTimeNaive`'s reference entry naming one of its two `undefined` cases, and
+  naming it as an equivalence: "Returns `undefined` when `startTime.resolvedDate` is `undefined`,
+  i.e. the file carries no resolvable date."
+  - It also returns `undefined` when `startTime.clockSource === 'none'` — the `hh.mm.ss` field
+    failed its grammar, so `startTime.clock` is a substituted midnight and there is no instant to
+    render. That case was added deliberately in 0.3.17, because a file whose starttime reads
+    `23.59.60` otherwise came back as `...T00:00:00.000`: a wall-clock instant the file never gave,
+    and for a sleep study the most believable start there is.
+  - `validation.md` and the source docblock both state it. The function's own reference page did
+    not, so a caller who checked `resolvedDate` first — exactly what the "i.e." invites — still got
+    `undefined` and had nothing to look up.
+- The entry now lists both conditions in a table and says which release added the second. The guard
+  checks the page names both **and** exercises the behaviour on a `23.59.60` file, so the page is
+  pinned to the code rather than to itself.
+
 ## 0.3.85
 
 - **Fixed** four pages denying a comparison the test suite performs on every run.

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.3.85";
+export declare const VERSION = "0.3.87";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.85';
+export const VERSION = '0.3.87';
 //# sourceMappingURL=constants.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.3.85",
+  "version": "0.3.87",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.3.85';
+export const VERSION = '0.3.87';