edfcore 0.3.61 → 0.3.62
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/CHANGELOG.md +18 -0
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/package.json +1 -1
- package/src/constants.ts +1 -1
package/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.3.62
|
|
10
|
+
|
|
11
|
+
- **Fixed** the Start-here page teaching `strict` with the one code family `strict` cannot fire on,
|
|
12
|
+
and printing that code's severity wrong.
|
|
13
|
+
- `concepts.md` showed `await openEdf(source, { strict: true })` producing
|
|
14
|
+
`EdfFormatError: [DATE_CLIPPED_TO_1985_2084]`. That never happens. `info` codes are exempt from
|
|
15
|
+
`strict` — `collector.ts` gates on `this.strict && diagnostic.severity !== 'info'` and says why
|
|
16
|
+
in the same docblock — and `DATE_CLIPPED_TO_1985_2084` is `info`. Run against a file whose only
|
|
17
|
+
defect is that code, `strict: true` resolves.
|
|
18
|
+
- Ten lines above, the same page printed `// warning DATE_CLIPPED_TO_1985_2084 168` as the output
|
|
19
|
+
of `console.log(diagnostic.severity, ...)`. The real first field is `info`.
|
|
20
|
+
- The `strict` example now uses `PATIENT_ID_NONCONFORMANT`, which is a warning and does throw, and
|
|
21
|
+
the page says out loud that `info` is exempt and why: nearly every EDF file carries this code,
|
|
22
|
+
so making `strict` throw on it would mean rejecting conforming files.
|
|
23
|
+
- The 0.3.39 guard could not see this. It matched `severity [CODE]` — the shape `formatDiagnostics`
|
|
24
|
+
emits — and this page prints the `console.log(severity, code, byteOffset)` shape instead. It now
|
|
25
|
+
checks both, so a page cannot state a severity the package would not print in either form.
|
|
26
|
+
|
|
9
27
|
## 0.3.61
|
|
10
28
|
|
|
11
29
|
- **Fixed** `inspectEdf` reporting a complete, perfectly readable file as `SOURCE_TOO_SMALL`, at
|
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.3.
|
|
112
|
+
export declare const VERSION = "0.3.62";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED