edfcore 0.4.355 → 0.4.356

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.355";
112
+ export declare const VERSION = "0.4.356";
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.355';
82
+ export const VERSION = '0.4.356';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,20 @@ 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.356
10
+
11
+ - **Added** an execution of the `resolveTimeWindow` example on `api-primitives.md`: a one-second
12
+ window from t = 2.5 on a file with one-second records, straddling records 2 and 3. The function
13
+ exists so the price of a window is auditable before a byte is read, and a reader planning a
14
+ viewport from that example is doing arithmetic that has to hold — including that two records are
15
+ paid for to get one second.
16
+ - The three ways to get nothing back are checked as well, since returning `[]` rather than throwing
17
+ is what lets a caller loop over ranges with no special case: a non-positive duration, a window
18
+ outside the recording, and one inside a gap on an index that knows where the gaps are. The last
19
+ is paired with the case either side of it, so the emptiness is about the gap rather than about
20
+ the file. And a probed index over a file with gaps throws rather than guessing at onsets nobody
21
+ has read.
22
+
9
23
  ## 0.4.355
10
24
 
11
25
  - **Fixed** a test of mine that could time out. The signature check added in 0.4.354 spawned `tsc`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.355",
3
+ "version": "0.4.356",
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.355';
96
+ export const VERSION = '0.4.356';