edfcore 0.6.51 → 0.6.52

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.51";
112
+ export declare const VERSION = "0.6.52";
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.51';
82
+ export const VERSION = '0.6.52';
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.6.52
10
+
11
+ - **Fixed** the `maxItems` row on `api-primitives.md`, both halves of which described something
12
+ `formatDiagnostics` does not do.
13
+ - "A non-finite value is ignored" stopped being true in 0.6.1, which made `NaN` a `RangeError`
14
+ and `-Infinity` show nothing rather than everything. `NaN` is non-finite and it is the value
15
+ that refusal exists for — `Number()` on an absent environment variable, query parameter or
16
+ config key — so the page was promising to swallow exactly what the library now refuses, and
17
+ naming the whole class the release split in two.
18
+ - "`0` shows only the summary line" described a line this function never prints. It renders one
19
+ block per diagnostic and nothing else, so `maxItems: 0` leaves the `... and N more` notice
20
+ alone. The summary belongs to `formatValidationReport`, whose own row on `api-helpers.md` says
21
+ so correctly — which is where the clause appears to have come from.
22
+ - The new test runs the function for each awkward value before reading the page for the claim, so
23
+ it fails on the behaviour as well as on the wording.
24
+
9
25
  ## 0.6.51
10
26
 
11
27
  - **Fixed** the README's account of what `--limit` caps. It said "Diagnostics and events print
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.51",
3
+ "version": "0.6.52",
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.51';
96
+ export const VERSION = '0.6.52';