edfcore 0.4.215 → 0.4.217

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.215";
112
+ export declare const VERSION = "0.4.217";
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.215';
82
+ export const VERSION = '0.4.217';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,23 @@ 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.217
10
+
11
+ - **Added** a check that `golden-values.test.ts` has a case for every committed golden that carries
12
+ samples. The list stays hand-written — each entry says why that file exists, which a directory
13
+ listing cannot — but it could fall behind `scripts/golden/generate.py`, and a golden generated
14
+ and committed with no entry is a pyEDFlib reference value nothing compares against. That is
15
+ indistinguishable from coverage until someone opens the directory.
16
+
17
+ ## 0.4.216
18
+
19
+ - **Changed** `diagnostic-docs.test.ts` to import `EdfDiagnosticDisposition` instead of declaring
20
+ its own identical union. It was the fifth copy of those four names and the one the compiler
21
+ trusted: every `as Disposition` in the file would have gone on compiling against a union that no
22
+ longer matched `codes.ts`, which is the opposite of what a cast is for. `SECTIONS` is now checked
23
+ against the real union — a heading with a disposition that does not exist is a type error naming
24
+ it, rather than a cast that quietly succeeds.
25
+
9
26
  ## 0.4.215
10
27
 
11
28
  - **Changed** the two severity patterns in `diagnostic-docs.test.ts` to come from the `EdfSeverity`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.215",
3
+ "version": "0.4.217",
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.215';
96
+ export const VERSION = '0.4.217';