edfcore 0.4.351 → 0.4.352

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.351";
112
+ export declare const VERSION = "0.4.352";
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.351';
82
+ export const VERSION = '0.4.352';
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.352
10
+
11
+ - **Added** `tests/property/window-cost.test.ts`, which states in general what four checks in this
12
+ batch pinned one file at a time. Each of those is a specific recording with a number beside it,
13
+ and each would keep passing if the rule behind it broke for every file except the one in the
14
+ example.
15
+ - The rule: for any well-formed continuous recording and any window that overlaps it, `readWindow`
16
+ issues exactly one read, and that read is a whole number of records. `byteLength` is asserted as
17
+ an identity rather than a bound — exactly the records the chunk reports, whatever fraction of
18
+ them the caller wanted — because that is what makes the number in the result worth publishing,
19
+ and it is what a per-signal narrowing would quietly break while still returning the right
20
+ samples.
21
+ - The third property is the general form of the table on `reading-signals.md`: asking for one
22
+ channel costs the same reads and the same bytes as asking for all of them, on arbitrary
23
+ geometries rather than on the three-signal file the page measures.
24
+
9
25
  ## 0.4.351
10
26
 
11
27
  - **Added** checks for two read counts on `api-reading.md`, a page that opens by inviting them:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.351",
3
+ "version": "0.4.352",
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.351';
96
+ export const VERSION = '0.4.352';