edfcore 0.3.49 → 0.3.50

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.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,28 @@ 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.3.50
10
+
11
+ - **Fixed** the "Renamed in 0.3.0" note in `api-helpers.md`, which was attached to the wrong family
12
+ of functions and so told a reader migrating from 0.2 to call a function that answers a different
13
+ question.
14
+ - The note sat at the end of **The recording-aware form**, saying that `sampleAt`,
15
+ `sampleStartTicksOf` and `sampleStartSecondsOf` "were `sampleIndexAt`, `sampleStartTicks` and
16
+ `sampleStartSeconds`" and that "the behaviour did not change". The rename table in
17
+ `migrating-to-0-3.md` and the 0.3.0 CHANGELOG entry both say those became **`gridSampleIndexAt`,
18
+ `gridSampleStartTicks` and `gridSampleStartSeconds`** — the family documented in the section
19
+ above.
20
+ - The two families are exactly the distinction the rename existed to make. On a six-record file
21
+ with a seven-second hole, `gridSampleStartSeconds(signal, 12, d)` is `3` and
22
+ `sampleStartSecondsOf(recording, i, 12)` is `10`. A reader who followed the note moved every
23
+ answer by the gaps, under a sentence promising nothing had changed. On a file with gaps and a
24
+ probed index, `sampleStartTicksOf` throws instead.
25
+ - The note now sits under the grid functions, and says out loud that the recording-aware family
26
+ below is a different one.
27
+ - `tests/integration/rename-note.test.ts` derives the rename from the migration table, checks the
28
+ CHANGELOG spells it the same way, and requires the code block the note is attached to to import
29
+ the names the table produces. A note that drifts onto the wrong family is a test failure.
30
+
9
31
  ## 0.3.49
10
32
 
11
33
  - **Fixed** `splitSubfields` splitting the EDF+ identification fields on JavaScript's `\s` instead
@@ -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.3.49";
112
+ export declare const VERSION = "0.3.50";
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.3.49';
82
+ export const VERSION = '0.3.50';
83
83
  //# sourceMappingURL=constants.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.3.49",
3
+ "version": "0.3.50",
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.3.49';
96
+ export const VERSION = '0.3.50';