edfcore 0.4.214 → 0.4.216

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.214";
112
+ export declare const VERSION = "0.4.216";
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.214';
82
+ export const VERSION = '0.4.216';
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.216
10
+
11
+ - **Changed** `diagnostic-docs.test.ts` to import `EdfDiagnosticDisposition` instead of declaring
12
+ its own identical union. It was the fifth copy of those four names and the one the compiler
13
+ trusted: every `as Disposition` in the file would have gone on compiling against a union that no
14
+ longer matched `codes.ts`, which is the opposite of what a cast is for. `SECTIONS` is now checked
15
+ against the real union — a heading with a disposition that does not exist is a type error naming
16
+ it, rather than a cast that quietly succeeds.
17
+
18
+ ## 0.4.215
19
+
20
+ - **Changed** the two severity patterns in `diagnostic-docs.test.ts` to come from the `EdfSeverity`
21
+ union rather than spelling out `error|warning|info`. They select the sample `formatDiagnostics`
22
+ lines in the pages that get checked against the code, so a fourth severity would have meant every
23
+ example using it was simply not looked at. Preventive rather than a fix: unlike the disposition
24
+ list in 0.4.214 there is no second inventory for severity to fall out of step with, so nothing is
25
+ wrong today and no canary demonstrates otherwise.
26
+
9
27
  ## 0.4.214
10
28
 
11
29
  - **Fixed** two hand-written copies of the disposition list in `diagnostic-docs.test.ts`. One was
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.214",
3
+ "version": "0.4.216",
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.214';
96
+ export const VERSION = '0.4.216';