edfcore 0.6.61 → 0.6.62

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.6.61";
112
+ export declare const VERSION = "0.6.62";
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.6.61';
82
+ export const VERSION = '0.6.62';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,19 @@ 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.6.62
10
+
11
+ - **Fixed** `api-errors.md` publishing `EdfFormatErrorInit` a field short. It was written
12
+ `{ code, diagnostic?, field?, byteOffset?, signalIndex?, recordIndex?, cause? }`, and the
13
+ interface also has `collected?`.
14
+ - `collected` is the one worth not losing: it carries the diagnostics the parse had already found
15
+ when one of them turned out to be fatal, which are often several that have nothing to do with
16
+ the fatal, and the fatal is frequently the least informative of the set. The same page
17
+ documents it two tables above, in the `EdfFormatError` field list — so the page explained the
18
+ field and then published an initialiser without it, which is the line a reader copies.
19
+ - The guard is generic, like 0.6.55's for tables: any `` `Name`: `{ … }` `` spelling in the docs
20
+ whose `Name` is an exported interface must list that interface's fields, in declaration order.
21
+
9
22
  ## 0.6.61
10
23
 
11
24
  - **Fixed** `api-errors.md` listing `name` among what a structured clone keeps. It keeps `message`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.61",
3
+ "version": "0.6.62",
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.6.61';
96
+ export const VERSION = '0.6.62';