edfcore 0.6.2 → 0.6.3

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

package/docs/CHANGELOG.md

@@ -6,6 +6,27 @@ 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.6.3
+
+- **Documented and pinned** what `JSON.stringify` does to a result, which is two different things
+  depending on which value you hand it. `design-decisions.md` already said ticks "do not survive
+  `JSON.stringify` without a replacer"; that is the loud half, and a caller adds a replacer and
+  moves on. The quiet half is that a replacer does not make the result JSON-safe: `Int32Array`
+  samples, `BigInt64Array` onsets and a diagnostic's `rawBytes` serialise as objects keyed by
+  numeric strings, and a property whose value is `undefined` is dropped rather than kept.
+- So a round trip returns something with no `.length` where the caller expects one, `toPhysical`
+  will not take it, and `'durationSeconds' in annotation` is true before and false after. Nothing
+  fails at the call site; it fails wherever the value is next indexed into.
+- `what-crosses-json.test.ts` is the sibling of `what-crosses-a-worker.test.ts` and gives the same
+  treatment to the boundary people actually use — a cache entry, a log line, a POST body. Over
+  every shape in the matrix it pins the exact split: a graph throws if and only if it holds a
+  `bigint` JSON would reach, an empty `BigInt64Array` included on the "no" side because there is no
+  element to refuse. Six of the values a caller reaches for throw and two do not, and the two that
+  do not are the ones with bytes rather than ticks in them.
+- The shape that works is the one `edfcore json` already emits — named primitive fields — and that
+  command is now checked as the worked example of it.
+- No behaviour changed.
+
 ## 0.6.2
 
 - **Fixed** a misspelled `redactFields` name being ignored. Redaction matches exactly against

package/package.json

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