edfcore 0.4.432 → 0.4.434

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

package/docs/CHANGELOG.md

@@ -6,6 +6,40 @@ 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.434
+
+- **Added** a check that asking a source for nothing costs nothing, in every adapter. A zero-length
+  read is what a caller gets from `end - start` when a window selects no samples, from a range
+  computed off a record count that turned out to be zero, or from a loop whose last iteration has
+  nothing left to take. `assertReadRange` allows it, so every adapter has to decide what to do with
+  it, and each decides separately.
+- The wrong answers are quiet ones. Handing the request to the transport gets a `bytes=100--1`
+  range no server will honour, or a `Blob.slice(100, 100)` and a promise allocated for nothing.
+  Neither is an error a caller could act on, and both are about a request nobody meant to make.
+- All five adapters are checked in one table rather than one at a time, because the contract is
+  about `ByteSource` and an adapter added later inherits it. The offset still has to be real:
+  `offset === byteLength` is legal, since that is where a read of nothing sits at the end of a
+  file, and past it the offset is outside the source whether or not any bytes would have been read.
+
+## 0.4.433
+
+- **Added** tests for what a conformant header is allowed to say. `validateHeader` raises three
+  advisory diagnostics about how a header is written, each checked somewhere for the case where it
+  fires, and none for the case where it stays quiet — which is the direction with consequences.
+- A conformance report is only worth reading if a clean file produces a short one. `PREFILTERING_NONE`
+  holds four spellings of "no filtering" that EDF+ and real writers use interchangeably, and
+  dropping one means every file from that writer carries a warning about a field it filled in
+  correctly. Nobody debugs that; they stop reading the warnings, which are the same warnings that
+  would have told them something real.
+- The headline is the whole of it at once: a header that follows EDF+ to the letter — an
+  `EEG Fpz-Cz` label, a named transducer, `HP:` and `LP:` terms — produces no conformance
+  diagnostics at all. That sentence is the product these checks exist to make possible and it was
+  never asserted.
+- One subtlety is pinned deliberately. A bare `EEG` label is flagged, because the rule is
+  `<type> <sensor>` and a type with no sensor names a category rather than a channel. The condition
+  that gets that right reads like a redundant length check beside the set membership next to it,
+  and simplifying it away would silently accept `EEG`, `ECG` and `Temp` as channel names.
+
 ## 0.4.432
 
 - **Added** a check that every version is still signed, and of the four lines that make it so.

package/package.json

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