edfcore 0.4.261 → 0.4.262
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 +14 -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.262";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,20 @@ 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.262
|
|
10
|
+
|
|
11
|
+
- **Fixed** the worked example on `annotations.md` — read the sample under each sleep-stage event
|
|
12
|
+
— which was the other complete program that failed to compile on nothing but an unnarrowed
|
|
13
|
+
index. It ended `toPhysical(signal, chunk.signals[0].digital)`, and `chunk.signals[0]` is
|
|
14
|
+
`T | undefined` under `noUncheckedIndexedAccess` even though the call asked for exactly one
|
|
15
|
+
signal. It narrows with a `continue` now, which is the shape the loop around it already uses
|
|
16
|
+
twice, and the numbered comment says the thing worth knowing: asking for one signal does not
|
|
17
|
+
tell the compiler you got one.
|
|
18
|
+
|
|
19
|
+
That closes both of the complete-but-unsound examples the 102-fence sweep in 0.4.261 turned up.
|
|
20
|
+
The rest of the site's failures are fragments referencing a `recording` or a `header` declared
|
|
21
|
+
in an earlier block on the same page, which is what a reference page is for.
|
|
22
|
+
|
|
9
23
|
## 0.4.261
|
|
10
24
|
|
|
11
25
|
- **Fixed** the opening example of `reading-signals.md`, which did not compile. It is the first
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED