edfcore 0.4.480 → 0.4.482
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 +32 -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.4.
|
|
112
|
+
export declare const VERSION = "0.4.482";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,38 @@ 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.482
|
|
10
|
+
|
|
11
|
+
- **Added** the `maxMaterializeBytes` boundary for `validateRecording`'s scan scratch buffer — the
|
|
12
|
+
fourth place in the package that compares a requirement against that budget, and the one
|
|
13
|
+
0.4.464 missed. That release pinned the other three by grepping for `resolveMaterializeBudget`;
|
|
14
|
+
this call site names its own variable, so the grep walked past it.
|
|
15
|
+
- The rule has to be the same in all four. A caller who sizes a request to the budget lands ON the
|
|
16
|
+
number, and a strict comparison here refuses the arithmetic the other three accept — for the one
|
|
17
|
+
option whose whole purpose is letting a caller state a ceiling and work up to it.
|
|
18
|
+
- Two records of ten samples need eighty bytes of `Int32Array`: a budget of eighty scans them, and
|
|
19
|
+
seventy-nine is refused with both numbers on the error. Relaxing the comparison now fails a test
|
|
20
|
+
instead of none.
|
|
21
|
+
|
|
22
|
+
## 0.4.481
|
|
23
|
+
|
|
24
|
+
- **Added** tests for the two overlaps `validate.ts` documents as deliberate. Its docblock names
|
|
25
|
+
`RECORD_SIZE_ABOVE_RECOMMENDED` and `PATIENT_ID_NONCONFORMANT` as codes the parser already
|
|
26
|
+
emits, re-checked here "so a validation report stands on its own instead of only making sense
|
|
27
|
+
next to `header.diagnostics`" — and neither had ever been produced by `validateHeader` in a
|
|
28
|
+
test. Both were covered through `parseHeader`, which is the other copy, so deleting either
|
|
29
|
+
function from this module left the suite green.
|
|
30
|
+
- A report that silently stopped standing on its own is the one failure that sentence exists to
|
|
31
|
+
prevent, and it is invisible: the codes are identical, so only the wording says which function
|
|
32
|
+
produced a diagnostic. Each case now asserts that the parser reports it, that `validateHeader`
|
|
33
|
+
reports it too, and that the two are distinguishable.
|
|
34
|
+
- The list is read out of the docblock rather than written into the test. A third overlap added to
|
|
35
|
+
that sentence without a case fails the first check, which is what stops the prose and the cover
|
|
36
|
+
drifting apart — the same shape of drift 0.4.455 found in a test name.
|
|
37
|
+
- The record-size boundary is pinned in both copies: 61,440 bytes exactly is not above the
|
|
38
|
+
recommendation. Narrowing that comparison warns every file that sized its records to the number
|
|
39
|
+
the specification names, which is the one size a careful writer would pick.
|
|
40
|
+
|
|
9
41
|
## 0.4.480
|
|
10
42
|
|
|
11
43
|
- **Added** membership checks inside the two directories the package actually ships.
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED