edfcore 0.4.503 → 0.4.504
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 +16 -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.504";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,22 @@ 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.504
|
|
10
|
+
|
|
11
|
+
- **Added** the values `api-primitives.md` prints beside each primitive. That page is the reference
|
|
12
|
+
for the layer under `openEdf`, and each entry ends with a line showing what comes back. Six of
|
|
13
|
+
them say something a reader would otherwise take on trust, and none was executed.
|
|
14
|
+
- Two are contracts rather than examples. `again.buffer === scratch.buffer` is the whole reason
|
|
15
|
+
`decodeDigital` takes an `out` argument — zero allocations after the first, in a loop over a long
|
|
16
|
+
recording. And `decodeHeaderLatin1(bytes.subarray(0, 8))` printing `'0 '` with its padding
|
|
17
|
+
intact is the "no trimming, no interpretation" promise the paragraph above it spends five
|
|
18
|
+
sentences on: a function that trimmed would satisfy every other test of it, because almost
|
|
19
|
+
everything else compares a decoded field against its trimmed value.
|
|
20
|
+
- `[ 0, 1 ]` from `findSignals` is the duplicate-label case the page annotates as something CHB-MIT
|
|
21
|
+
really does, and the reason `getSignal` has an ambiguity error at all. The sentence beside it —
|
|
22
|
+
the argument is trimmed, the match is case-sensitive, nothing else is normalised — is asserted
|
|
23
|
+
with it.
|
|
24
|
+
|
|
9
25
|
## 0.4.503
|
|
10
26
|
|
|
11
27
|
- **Added** the two snippets on `api-reading.md` that print values — what `openEdf` reports for an
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED