edfcore 0.4.359 → 0.4.361

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

package/docs/CHANGELOG.md

@@ -6,6 +6,36 @@ 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.361
+
+- **Added** a check over the error-class table on `api-errors.md`. Seven classes, each with an
+  `edfErrorKind` — the field a caller branches on, since `instanceof` is false across a realm
+  boundary — so the table is the map between the class you catch and the string you switch on. Each
+  row now has a fixture that produces the condition it describes, so none is checked by assertion
+  alone, and a class whose kind changed would otherwise fall silently into a different branch of
+  every consumer's handler.
+- The distinction below the table is checked too. An error raised from a diagnostic opens with its
+  code in brackets; `EdfDiagnostic.message` does not, because `formatDiagnostics` renders the code
+  from the field beside it. Prefixing `error.code` when displaying a diagnostic therefore prints it
+  twice, which is what the inspector on this site did until 0.4.185 — a convention, and a
+  convention is what the next message quietly breaks.
+
+## 0.4.360
+
+- **Added** checks for the two things `toPhysicalEnvelope` does that `toPhysical` must not be used
+  for. A bucket no sample landed in carries a digital `0`, because `min` and `max` are
+  `Int32Array`s and cannot hold a sentinel — and through the affine map that becomes mid-scale for
+  any channel whose range is not centred on zero. On the 0..1000 channel the page names it is 500,
+  which is now computed from the scale rather than quoted: a completely believable reading, drawn
+  as a flat trace across a hole.
+- That failure is worth a test precisely because everything about it looks right — the number is
+  inside the channel's range, the arrays agree in length, the trace is continuous, and the only
+  sign is a stretch nobody sampled drawn as a steady midpoint. Both arrays now have to be `NaN`
+  wherever `counts` is zero, and `counts` itself has to be untouched.
+- The second is polarity: a negative gain makes the map decreasing, so mapping `min` to `min`
+  yields an envelope drawn inside out. Every filled bucket on such a channel is checked to come
+  back with its lower bound below its upper one.
+
 ## 0.4.359
 
 - **Added** a check for the two bucket-count rules on `api-helpers.md`. `readEnvelope` clamps

package/package.json

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