edfcore 0.4.374 → 0.4.375

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
109
109
  readonly reserved: 224;
110
110
  };
111
111
  /** Published package version. Kept in sync with package.json by a test. */
112
- export declare const VERSION = "0.4.374";
112
+ export declare const VERSION = "0.4.375";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.374';
82
+ export const VERSION = '0.4.375';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ alone does not tell you whether you were affected.
6
6
  edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
7
7
  defect; those are called out below.
8
8
 
9
+ ## 0.4.375
10
+
11
+ - **Added** `tests/property/read-agreement.test.ts`: the two ways to read the same records return
12
+ the same samples. `readWindow` resolves a time window and splits it; `readRecords` is handed a
13
+ range directly. Every worked example in the documentation uses whichever is more convenient, so a
14
+ caller who computes a range with `resolveTimeWindow` and reads it with `readRecords` has to get
15
+ exactly what `readWindow` would have returned — and nothing said so.
16
+ - Each has thorough tests of its own and they share a decoder, but the layer above the decoder is
17
+ separate, and a divergence there is not a decode bug: the samples would be individually correct
18
+ and attached to the wrong records, which is the failure mode this package treats as the worst
19
+ kind because nothing about the numbers looks wrong.
20
+ - So the fixture's generator makes every sample a function of its own record and position, and the
21
+ second property checks each returned value against where the chunk says it came from — over
22
+ arbitrary geometries, since the interesting windows are the awkward ones: shorter than a record,
23
+ starting mid-record, running off the end.
24
+
9
25
  ## 0.4.374
10
26
 
11
27
  - **Added** a check over what `installation.md` says each entry point contains. The page names
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.374",
3
+ "version": "0.4.375",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.374';
96
+ export const VERSION = '0.4.375';