edfcore 0.6.87 → 0.6.88

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.6.87";
112
+ export declare const VERSION = "0.6.88";
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.6.87';
82
+ export const VERSION = '0.6.88';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.6.88
10
+
11
+ - **Fixed** the last two places on the inspector that read a tick-derived number as a float: the
12
+ summary's Duration and the status line under the file name, both `hhmmss(timeline.spanSeconds)`.
13
+ `EdfTimeline` says which field carries a span — "the ticks are what it must be asked of" — and
14
+ the Duration is the headline number on that summary.
15
+ - It fails the way the event clock did in 0.6.82: one tick short of a whole second, at a scale
16
+ where a tick is below the float's ulp, `spanSeconds` rounds up and flooring it names a recording
17
+ a second longer than it is.
18
+ - The test is a sweep rather than a fourth one-off. It strips the page's comments and asserts that
19
+ no `*Seconds` field is handed to a clock or compared against another, so a fourth site cannot be
20
+ added quietly — and it found the status line, which was not the one being fixed. The scrub
21
+ controls keep their seconds: those are range inputs read with `Number(...)`, with no exact value
22
+ behind them to lose.
23
+
9
24
  ## 0.6.87
10
25
 
11
26
  - **Changed** what `readWindow`, `readEnvelope` and `streamRecords` say when handed a `{ records }`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.87",
3
+ "version": "0.6.88",
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.6.87';
96
+ export const VERSION = '0.6.88';