edfcore 0.3.62 → 0.3.64
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 +33 -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,39 @@ 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.64
|
|
10
|
+
|
|
11
|
+
- **Fixed** the pre-0.2 status text still on the website, which contradicted the package and, in one
|
|
12
|
+
case, the page it linked to in the same sentence.
|
|
13
|
+
- `concepts.md` said the pyEDFlib comparison harness "does not exist yet in 0.1" and linked, in
|
|
14
|
+
that sentence, to `physical-values.md`, which says it has existed since 0.2.34-0.2.48. So the
|
|
15
|
+
one claim a reader would check was denied by the page they were sent to check it on.
|
|
16
|
+
- `installation.md` said "edfcore is at 0.1.0" and that an element-by-element comparison against
|
|
17
|
+
pyEDFlib is "still missing"; `api-primitives.md` tabled `VERSION` as `'0.1.0'` and repeated it
|
|
18
|
+
in prose as "at the time of writing".
|
|
19
|
+
- Three pages scoped a still-true statement to a dead series — "edfcore has no other lifetime
|
|
20
|
+
mechanism in 0.1". The claim holds (`Symbol.asyncDispose` is not Baseline); the version scope
|
|
21
|
+
did not.
|
|
22
|
+
- The `VERSION` row no longer spells a number at all. A version written into a table is stale the
|
|
23
|
+
next release, which is how this started.
|
|
24
|
+
- `tests/integration/readme-status.test.ts` now sweeps every docs page for two present-tense shapes:
|
|
25
|
+
"edfcore is at X.Y.Z" that is not the published version, and "in X.Y" scoping a claim to a series
|
|
26
|
+
that is no longer this one. Past-tense history — "renamed in 0.3.0", "fixed in 0.2.63", "since
|
|
27
|
+
0.2.34-0.2.48" — is correct forever and is deliberately not matched.
|
|
28
|
+
|
|
29
|
+
## 0.3.63
|
|
30
|
+
|
|
31
|
+
- **Fixed** `diagnostics.md`'s always-fatal table, which said "Nine codes are always fatal", listed
|
|
32
|
+
**eight**, and then said "All eight throw `EdfFormatError`".
|
|
33
|
+
- The missing row was `RECORDING_SPAN_UNREPRESENTABLE` — `recordCount × recordDuration` beyond the
|
|
34
|
+
signed 64-bit tick range, so the later records have no representable start. It is in
|
|
35
|
+
`api-errors.md`'s own always-fatal table, so the package's two diagnostic pages disagreed about
|
|
36
|
+
how many always-fatal codes there are.
|
|
37
|
+
- The 0.3.39 guard checked the prose count on this page and the tables on `api-errors.md`, but not
|
|
38
|
+
this page's table — which is why the count and the rows under it could drift apart. It now
|
|
39
|
+
requires every `fatal` code in `codes.ts` to have a row here, requires every row to actually be
|
|
40
|
+
fatal, and requires the "All N throw" sentence to spell the number the source has.
|
|
41
|
+
|
|
9
42
|
## 0.3.62
|
|
10
43
|
|
|
11
44
|
- **Fixed** the Start-here page teaching `strict` with the one code family `strict` cannot fire on,
|
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.64";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/package.json
CHANGED
package/src/constants.ts
CHANGED