edfcore 0.6.148 → 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.
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/docs/CHANGELOG.md +8 -0
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/dist/constants.d.ts
CHANGED
|
@@ -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.
|
|
112
|
+
export declare const VERSION = "0.6.149";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,14 @@ 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
|
+
|
|
9
17
|
## 0.6.148
|
|
10
18
|
|
|
11
19
|
- **Documented** the rule 0.6.130 and 0.6.140 introduced: the options argument itself has to be an
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED