edfcore 0.4.458 → 0.4.459

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

package/docs/CHANGELOG.md

@@ -6,6 +6,23 @@ 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.4.459
+
+- **Added** the two `COMMA_DECIMAL_SEPARATOR` cases that were missing: a comma in the declared
+  header size, and a comma in the record count.
+- `readNumericField` exists for exactly those two fields, because both have an authoritative
+  alternative — the computed header size always wins, and the record count is recoverable from the
+  source length. Both were tested only with values that recover, so the one line in that function
+  which does NOT recover had never run. Deleting it changed nothing visible: the comma fell through
+  to `!parse.ok`, became `NaN`, and was quietly replaced.
+- That silence is what the refusal is for. `"1,024"` in the record count is one thousand and
+  twenty-four records to the writer that wrote it; recovering from the source length yields a
+  plausible number that is right only by accident, and `recordCount` is what every read range in
+  the library is checked against.
+- The contrast is asserted alongside it — any other bad value in those two fields still recovers,
+  with `RECORD_COUNT_RECOVERED` or `HEADER_SIZE_MISMATCH` — so the new cases pin the comma as the
+  exception rather than pinning the fields as fatal.
+
 ## 0.4.458
 
 - **Added** tests for a bad HTTP status during a READ, which had never run. `httpSource` reports a

package/package.json

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