edfcore 0.4.387 → 0.4.388

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.387";
112
+ export declare const VERSION = "0.4.388";
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.387';
82
+ export const VERSION = '0.4.388';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,24 @@ 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.388
10
+
11
+ - **Fixed** the figure three places give for the size of this suite. The README said 1,900 or more
12
+ tests, the note at the foot of `installation.md` said 1,200 or more, and the docblock of
13
+ `browser-safety.test.ts` said 1,900-odd — three figures for one fact, the smallest of them eight
14
+ hundred behind. All three now say 2,000.
15
+ - None of them was ever false, which is why nothing caught them. A claim of the form "N or more"
16
+ stays true forever once it is true, and the property that makes it safe is the property that
17
+ makes it worthless: it can never be wrong, so it is never re-read. What a reader takes from it is
18
+ a sense of scale, and half the real scale is a wrong impression conveyed in a true sentence.
19
+ - **Added** the check that keeps it current: the figure has to be one figure wherever it is stated,
20
+ and no smaller than the number of `it(...)` and `test(...)` declarations the suite writes out. It
21
+ fails when the suite grows past what the pages claim, which is the direction this rots in.
22
+ - It does not check the other direction. Four dozen of those declarations are `it.each(...)`,
23
+ expanding at run time to one case per row, so the count read out of the files is a floor rather
24
+ than the total — the right side to be wrong on, since a figure that clears it is true of the real
25
+ total too, but nothing here would notice one inflated past both.
26
+
9
27
  ## 0.4.387
10
28
 
11
29
  - **Added** a check that the published `bin` runs as a program. `cli.test.ts` and the rest drive
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.387",
3
+ "version": "0.4.388",
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.387';
96
+ export const VERSION = '0.4.388';