edfcore 0.5.27 → 0.5.29

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

package/docs/CHANGELOG.md

@@ -6,6 +6,55 @@ 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.5.29
+
+- **Added** the contract `signalIndices` has to keep at all five reads that take one.
+  `duplicate-signal-indices.test.ts` covers two of the rules `api-reading.md` states — duplicates are
+  dropped, the order given is the order returned — over `readRecords`, `readWindow` and
+  `streamRecords`. It does not reach the two envelope entry points, and nothing covered what the
+  option does when it is wrong.
+- The refusals are the part worth pinning, because there are two of them and they are deliberately
+  different classes. An index the file does not have is an `EdfChannelNotFoundError`, an `EdfError`
+  carrying `selector` and `availableLabels` so a caller can offer the right one. An index naming the
+  annotations channel is a plain `RangeError`, because it can only be a caller's mistake and never a
+  file's — the bytes there are TAL text, and decoding them as samples produces numbers that look
+  exactly like a signal. `isEdfError` is the split, and a caller writing one `catch` for bad files
+  and another for bad calls depends on it holding at every entry point rather than at the one they
+  tested against.
+- There is no reason for five functions to diverge — they share `resolveSignals` — which is exactly
+  why it is worth a test: a sixth entry point, or one that grows its own validation to report
+  something friendlier, is how a shared rule stops being one. All nine functions in `src/` that take
+  a `signalIndices` are enumerated by resolving their parameter types, and split into the five under
+  test, the two shared helpers, and the two annotation reads whose `signalIndices` selects annotation
+  signals and inverts both rules.
+- Nine cases run at every one of the five: out of range, negative, fractional, the annotations
+  channel alone and mixed with a real signal, a repeat, a repeat out of order, a reversal, and an
+  empty selection — which returns no signals rather than all of them.
+
+## 0.5.28
+
+- **Added** an already-aborted signal driven through every entry point that takes one.
+  `api-sources.md` says edfcore "polls `.aborted` before and after each read and throws an `Error`
+  whose `name` is `'AbortError'`"; `data-sources.md` adds that every bundled adapter checks it
+  before it starts, and that the rejection "is a plain `Error` ... not an `EdfError`.
+  `isEdfError` returns false for it, so a `catch` that re-throws aborts stays simple."
+- `http-abort-signal.test.ts` covers the adapter with the most to go wrong. What nothing covered is
+  the sentence's scope. The guard lives in the SOURCES, and every reading function reaches it only
+  by issuing a read — so whether each of them actually does, before allocating, before scanning,
+  before decoding, is a property of thirteen call paths rather than of the four adapters. A function
+  that resolved its window or sized its buffer first would do that work for a caller who had already
+  cancelled.
+- All thirteen are now driven, and each must reject with `name === 'AbortError'` and `isEdfError`
+  false — the discriminator the page says consumers branch on, chosen because `DOMException` cannot
+  be named without the DOM lib. The four adapters are driven directly alongside them, and each is
+  also shown to read normally when the signal is simply not aborted.
+- The one place it does not fire is checked with them, because it is documented rather than
+  accidental: `api-reading.md` says a record range with `count: 0` "issues no read at all", and a
+  call that reads nothing has nothing to abort.
+- The last block is the other half of `ReadOptions`' own docblock — "cancelling a read and capping an
+  allocation never alter what a completed call returns". A signal that is never aborted leaves every
+  result identical to one passed no options at all.
+
 ## 0.5.27
 
 - **Added** a non-finite bound driven through every entry point that takes a time in seconds.

package/package.json

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