edfcore 0.4.411 → 0.4.413

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

package/docs/CHANGELOG.md

@@ -6,6 +6,41 @@ 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.413
+
+- **Added** tests for the calendar edfcore validates against. `isValidCalendarDate` exists because
+  a `Date` is the wrong tool: real files carry 31 April and 29 February in common years, and
+  `new Date(1997, 3, 31)` rolls both forward into a neighbouring month rather than rejecting them.
+  A recording silently dated a day later than it was made is the kind of error nobody finds,
+  because the wrong answer is a perfectly ordinary date.
+- `date-ban.test.ts` proves no `Date` is constructed anywhere. That left the arithmetic which
+  replaced it, exercised only through the parser, where a rejected date is indistinguishable from a
+  rejected field.
+- The month lengths are not restated — restating a table checks a transcription, and the
+  transcription is what would already be wrong. The properties it must satisfy are checked instead,
+  from the Gregorian calendar rather than from this file: the twelve months sum to 365 or 366 for
+  every year from 1 to 9999; four hundred consecutive years hold exactly 97 leap years and 146,097
+  days, which is a whole number of weeks; and a century not divisible by 400 holds 24, not 25.
+- A table with a month a day short fails the first for every year, and a leap rule missing its
+  century exception fails the second by three days a cycle.
+
+## 0.4.412
+
+- **Added** tests for four header fields that are all finite and imply a gain that is not. An EDF
+  physical bound is eight bytes of ASCII, which is room for an exponent, so a physical range can
+  underflow against the digital range — `0` to `5E-324` over -1..1 puts `bitValue` at zero and
+  `offset` at infinity — or overflow it, where `-9.9E307` to `9.9E307` exceeds float64 before the
+  division happens.
+- Nothing about such a file looks wrong. The header parses, every field is in range for its width,
+  and a reader who does not check `signal.scale` gets a column of `NaN` where microvolts should be
+  — which plots as an empty panel, or silently poisons a mean. The scale is refused exactly as the
+  obvious degeneracies are, and `decodeDigital` keeps working, which is the whole reason
+  `toPhysical` is a separate call.
+- A signal declaring a negative `samplesPerRecord` is the other shape of "parses and cannot be
+  used", and it is fatal rather than diagnosed: every later signal's byte offset inside a record is
+  a running sum of that field, so a negative one does not make one signal wrong, it makes every
+  signal after it point at the wrong bytes.
+
 ## 0.4.411
 
 - **Added** tests for the envelope of the files and selections a viewer produces by accident.

package/package.json

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