edfcore 0.4.344 → 0.4.345

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.344";
112
+ export declare const VERSION = "0.4.345";
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.344';
82
+ export const VERSION = '0.4.345';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.345
10
+
11
+ - **Added** a check that the six single-interface field tables on `api-types.md` list exactly the
12
+ members those interfaces have, in declaration order. That page is the field-by-field reference
13
+ and where someone goes to learn what is on an `EdfHeader` without opening `types.ts`, and all six
14
+ tables are hand-typed copies of a declaration.
15
+ - Both directions of drift are silent. A member added to `types.ts` and not to the page is a field
16
+ nobody can discover — which is how `declaredRecordCount` or `recordCountSource` would go unused
17
+ by exactly the caller who needed them. A row for a member that no longer exists is worse: it
18
+ reads as an API, the reader writes `header.something`, and the answer is `undefined` rather than
19
+ an error. `docs-coverage.test.ts` proves every export is mentioned; nothing had looked inside a
20
+ type.
21
+ - One table spans three interfaces and cannot have its rows attributed to any one of them, so it
22
+ is skipped by name and the number of skipped tables is asserted — an exemption that cannot
23
+ quietly grow.
24
+
9
25
  ## 0.4.344
10
26
 
11
27
  - **Added** a check over what `data-sources.md` publishes about `cachedSource`. `cache.test.ts`
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.344",
3
+ "version": "0.4.345",
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.344';
96
+ export const VERSION = '0.4.345';