edfcore 0.5.50 → 0.5.52

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

package/docs/CHANGELOG.md

@@ -6,6 +6,53 @@ 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.52
+
+- **Added** the sweep for a selection that came from JSON. `io/read.ts` says why this is not a
+  type-system question: "`records` is typed, and the type is not the only way in: a selection built
+  from JSON, from a config file or from a JavaScript call site arrives at run time." It then records
+  what used to happen — every wrong shape reached a refusal with a next step, "while `undefined` and
+  `null` threw `TypeError: Cannot read properties of undefined (reading 'start')` ... which names
+  neither the option nor anything to do about it" (fixed in 0.4.443).
+- That is a whole class and it had one test. A saved view, a URL parameter, a job on a queue: all of
+  them arrive as `JSON.parse` output, where a number written as a string stays a string and an
+  omitted field is simply absent. `record-range-contract.test.ts` covers ranges that are well formed
+  and out of bounds; this covers ranges that are not ranges.
+- Nine malformed `records` shapes — absent, null, empty, half-filled, an array, a string,
+  string-valued fields, a null field — are each refused at all three entry points with an
+  `EdfRangeError` carrying the same next step, and absent and null are asserted not to raise the
+  `TypeError` they once did. A valid range survives a JSON round-trip, extra properties and all.
+- Four malformed `signalIndices` shapes are a plain `RangeError`, since a selection that is not an
+  array is a caller's mistake and not a file's.
+- One shape is accepted, and it is named rather than left to be discovered: an array holding the
+  canonical decimal string for an index — `['0']`, which is what `JSON.parse('["0"]')` from a query
+  string gives — resolves to that signal. It is ordinary array-index coercion and it is tight:
+  `'00'`, `' 0'`, `'0.0'`, `'+0'` and a label are each an `EdfChannelNotFoundError` naming the
+  selector verbatim, and the chunk reports `signalIndex` as a number, so nothing downstream carries
+  the string.
+
+## 0.5.51
+
+- **Added** the promise `annotations.md` makes about partial reads, and the thing it costs.
+  `readAnnotations` "supplies the rebasing origin from the timeline, so a partial range answers the
+  same as a whole-file one" — and could not derive that origin on its own, because "a range that
+  does not contain record 0 has to infer it from an observed onset, which only works while the
+  records in between are contiguous". Before 0.2.28 the pairing the page recommends,
+  `readAnnotations(recording, chunk.records)`, reported the same event a quarter of a second later
+  than a whole-file decode did.
+- Three behaviours, one of them a defect that shipped, and none under test: `readAnnotations` was
+  checked on whole files and on single ranges, and nothing partitioned a file and compared.
+- The property runs first. For any partition of the record range into contiguous pieces, the reads
+  concatenate to the whole-file read — every field of every event, both axes, both exact tick counts
+  and `recordOnsetTicks` — over a contiguous file, one with a quarter-second start offset, and an
+  EDF+D file with a twenty-second hole.
+- Then the three-way comparison that shows the origin doing the work, on the post-gap range of that
+  EDF+D file. `readAnnotations` puts the event at 26.5 s on the record axis. `decodeAnnotations`
+  called directly on the same bytes puts it at 26.75 — its inferred origin lands outside `[0, 1)`,
+  so rebasing switches off and the two axes come back equal, exactly as documented. Passing
+  `startOffsetTicks` by hand restores 26.5. And on the same shape without the hole the inference
+  works unaided, which is what makes the failure about EDF+D rather than about partial ranges.
+
 ## 0.5.50
 
 - **Added** three ways a header can be written and mean the same thing. Each is documented, each is

package/package.json

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