edfcore 0.6.147 → 0.6.149

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.147";
112
+ export declare const VERSION = "0.6.149";
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.147';
82
+ export const VERSION = '0.6.149';
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.6.149
10
+
11
+ - **Documented** that `redactFields` takes a list, not a name — the rule 0.6.143 made enforceable,
12
+ on both pages that tell a reader to use it.
13
+ - Every example spells it `['patientId', 'recordingId']` and neither page said the brackets were
14
+ load-bearing. A string is iterable, so the bare name walked its characters and reported `"p"`.
15
+ - The CLI page carries it too, since that is where the redaction argument is actually made.
16
+
17
+ ## 0.6.148
18
+
19
+ - **Documented** the rule 0.6.130 and 0.6.140 introduced: the options argument itself has to be an
20
+ object, in the three formatters and in `cachedSource`.
21
+ - Both pages described the FIELDS and neither described the argument, which is the whole of the
22
+ defect — `formatAnnotations(annotations, 20)` had no `maxItems` on it, so the limit read as
23
+ absent and every annotation printed with nothing saying so.
24
+ - `undefined` and `null` still mean "no options", and the tables say so.
25
+
9
26
  ## 0.6.147
10
27
 
11
28
  - **Documented** the `out` rules 0.6.134 and 0.6.145 introduced, on the page that describes `out`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.147",
3
+ "version": "0.6.149",
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.147';
96
+ export const VERSION = '0.6.149';