edfcore 0.6.148 → 0.6.150

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.148";
112
+ export declare const VERSION = "0.6.150";
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.148';
82
+ export const VERSION = '0.6.150';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,24 @@ 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.150
10
+
11
+ - **Documented** what "duplicates are dropped" is decided on. `api-reading.md` stated the rule and
12
+ not the value it reads: 0.6.135 moved it to the index a selection RESOLVES to, because holding
13
+ the values as written left `[0, '0']` deduplicated against nothing.
14
+ - The page also now says that an array-index string resolves to its signal, which is what
15
+ `JSON.parse` of a query string gives, and that mixing is how it arrives.
16
+ - The record range beside it is covered too: refused rather than coerced, and since 0.6.137 printed
17
+ field by field as it was written.
18
+
19
+ ## 0.6.149
20
+
21
+ - **Documented** that `redactFields` takes a list, not a name — the rule 0.6.143 made enforceable,
22
+ on both pages that tell a reader to use it.
23
+ - Every example spells it `['patientId', 'recordingId']` and neither page said the brackets were
24
+ load-bearing. A string is iterable, so the bare name walked its characters and reported `"p"`.
25
+ - The CLI page carries it too, since that is where the redaction argument is actually made.
26
+
9
27
  ## 0.6.148
10
28
 
11
29
  - **Documented** the rule 0.6.130 and 0.6.140 introduced: the options argument itself has to be an
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.148",
3
+ "version": "0.6.150",
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.148';
96
+ export const VERSION = '0.6.150';