edfcore 0.6.76 → 0.6.77

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.76";
112
+ export declare const VERSION = "0.6.77";
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.76';
82
+ export const VERSION = '0.6.77';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ 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.77
10
+
11
+ - **Fixed** the `EdfAnnotation` example on `api-types.md`, which listed `onsetTicks` with the
12
+ comment "compare with this" and did not list `onsetTicksFromFirstRecord` at all.
13
+ - The table four lines below it says the opposite — the rebased field is "the axis `readWindow`,
14
+ `readEnvelope` and `segment.startTicks` use" — and `types.ts` calls `onsetTicks` the wrong one
15
+ for comparing an annotation against a window. This is the defect 0.6.56 fixed in
16
+ `tal/annotations.ts`, in the place a reader copies from rather than the place they read.
17
+ - The example compounded it: both fields print `15000000n` there, because that file declares no
18
+ sub-second start offset. That is most files, and exactly why an example is the worst place to
19
+ learn which field to use. A note now says so, and the test builds a file with an offset and
20
+ shows the two differing by it.
21
+
9
22
  ## 0.6.76
10
23
 
11
24
  - **Fixed** the inspector placing each sample at `part.startSeconds + i / rate`, over a rate it
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.76",
3
+ "version": "0.6.77",
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.76';
96
+ export const VERSION = '0.6.77';