edfcore 0.3.89 → 0.3.90
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 +19 -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,25 @@ 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.90
|
|
10
|
+
|
|
11
|
+
- **Fixed** three more pages carrying claims two earlier releases retired, and **widened both
|
|
12
|
+
guards** so they match the claim rather than one phrasing of it.
|
|
13
|
+
- `api-errors.md` said the first would-be diagnostic "of *any* disposition throws" and that this
|
|
14
|
+
is "why every `diagnostics` array is empty by construction in strict mode". `diagnostics.md`
|
|
15
|
+
said the same in different words. Both are the claim 0.3.76 removed from three other places:
|
|
16
|
+
`info` is exempt, and a strict parse of a file whose only note is `info` resolves carrying it.
|
|
17
|
+
- `large-files.md` called `buildRecordIndex` "the one call in edfcore that does traverse the whole
|
|
18
|
+
file" — the claim 0.3.83 corrected on two other pages. `validateRecording` is the other.
|
|
19
|
+
- The guards are the real defect here. 0.3.76 pinned the exact strings it happened to find
|
|
20
|
+
(`consequently empty`, `exempts nothing`) and 0.3.83 pinned `only function in edfcore that reads
|
|
21
|
+
the whole file`. Every page that said the same thing in slightly different words walked straight
|
|
22
|
+
past them — which is how a sixth sweep found them as fresh findings rather than the suite catching
|
|
23
|
+
them. Both now match the claim: any spelling of "every diagnostics array is empty", and any
|
|
24
|
+
spelling of "only one function/call reads or traverses the whole file".
|
|
25
|
+
- A guard written around the instance you just fixed is a guard that catches nothing else. Widening
|
|
26
|
+
these two turned up all three of these pages immediately.
|
|
27
|
+
|
|
9
28
|
## 0.3.89
|
|
10
29
|
|
|
11
30
|
- **Fixed** the envelope budget guard measuring 12 bytes per bucket while the fixed-width path
|
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.90";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED