edfcore 0.4.325 → 0.4.326

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.325";
112
+ export declare const VERSION = "0.4.326";
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.325';
82
+ export const VERSION = '0.4.326';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,21 @@ 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.326
10
+
11
+ - **Added** the last unchecked section of `physical-values.md`: the four conditions that leave a
12
+ signal with no scale. Each row's code is produced by building the signal the row describes and
13
+ catching what `toPhysical` refuses it with, and the table's introduction — "checked in this
14
+ order" — is exercised against signals that trip two conditions at once, because the order is
15
+ what decides which code such a signal reports.
16
+ - The page's second verbatim message block is pinned the way 0.4.316 pinned the first: only the
17
+ hard wraps are undone, since the runs of spaces inside it are the raw eight-byte fields quoted as
18
+ the file holds them. Also checked is the asymmetry the section turns on — an inverted physical
19
+ range keeps its scale, because a negative amplifier gain has a documented meaning, and an
20
+ inverted digital range does not and is refused.
21
+ - With this, `edf-format.md` and `physical-values.md` are no longer the two pages nothing in the
22
+ suite reads.
23
+
9
24
  ## 0.4.325
10
25
 
11
26
  - **Added** a check for the claim `edf-format.md` closes with: "Every diagnostic edfcore emits
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.325",
3
+ "version": "0.4.326",
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.325';
96
+ export const VERSION = '0.4.326';