edfcore 0.6.51 → 0.6.53

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.6.51";
+export declare const VERSION = "0.6.53";
 //# 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.6.51';
+export const VERSION = '0.6.53';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,35 @@ 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.6.53
+
+- **Fixed** the `EdfLocation` table on `api-types.md`, which listed three of the shape's five
+  fields. The two it dropped were `recordStartTicks` and `offsetInRecordTicks`.
+- Those are the exact halves. The `EdfSegment` and `EdfGap` tables immediately above it pair every
+  `*Seconds` with its `*Ticks` twin, and the paragraph between them says to prefer the ticks:
+  "Every second on these two is a float64 conversion of the tick beside it. Compare and sum the
+  ticks." The next table then showed a reader only the float64 half of the one shape
+  `index.locate()` returns — the call whose whole job is to hand you a position to read from.
+- The rows are added and the paragraph's rule is restated under them. The test reads the fields
+  off a real `locate()` result rather than off the type, so the table is compared with the object
+  a caller receives.
+
+## 0.6.52
+
+- **Fixed** the `maxItems` row on `api-primitives.md`, both halves of which described something
+  `formatDiagnostics` does not do.
+- "A non-finite value is ignored" stopped being true in 0.6.1, which made `NaN` a `RangeError`
+  and `-Infinity` show nothing rather than everything. `NaN` is non-finite and it is the value
+  that refusal exists for — `Number()` on an absent environment variable, query parameter or
+  config key — so the page was promising to swallow exactly what the library now refuses, and
+  naming the whole class the release split in two.
+- "`0` shows only the summary line" described a line this function never prints. It renders one
+  block per diagnostic and nothing else, so `maxItems: 0` leaves the `... and N more` notice
+  alone. The summary belongs to `formatValidationReport`, whose own row on `api-helpers.md` says
+  so correctly — which is where the clause appears to have come from.
+- The new test runs the function for each awkward value before reading the page for the claim, so
+  it fails on the behaviour as well as on the wording.
+
 ## 0.6.51
 
 - **Fixed** the README's account of what `--limit` caps. It said "Diagnostics and events print

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.6.51",
+  "version": "0.6.53",
   "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.6.51';
+export const VERSION = '0.6.53';