edfcore 0.4.372 → 0.4.374
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 +33 -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.374";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/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.4.374
|
|
10
|
+
|
|
11
|
+
- **Added** a check over what `installation.md` says each entry point contains. The page names
|
|
12
|
+
roughly twenty functions across three paragraphs as the answer to "what do I get if I import
|
|
13
|
+
this", and a name in that list that is not an export sends a reader to an import error on their
|
|
14
|
+
first line. It is also checked to name nothing that lives behind `edfcore/node`, which is the
|
|
15
|
+
claim the whole browser story rests on.
|
|
16
|
+
- The exports map is printed as JSON — not a description of `package.json` but `package.json`,
|
|
17
|
+
retyped, which is the strongest form of a copy and the easiest to let drift. `publint` and
|
|
18
|
+
`packaging-claims.test.ts` check the real map for shape and for the absence of environment
|
|
19
|
+
conditions; neither can see that the page prints the same three entries. It is now parsed and
|
|
20
|
+
compared entry for entry, and the six condition names the page lists are checked against the
|
|
21
|
+
manifest.
|
|
22
|
+
- "Two functions" for `edfcore/node` is asserted as an exact count rather than a floor: that entry
|
|
23
|
+
point exists to be the only module a browser build must not reach, so every name added to it is
|
|
24
|
+
another thing a bundler has to be kept away from.
|
|
25
|
+
|
|
26
|
+
## 0.4.373
|
|
27
|
+
|
|
28
|
+
- **Added** a cross-check between the two tables of the four onset fields — `annotations.md` lists
|
|
29
|
+
them by axis, `api-helpers.md` under "Which onset field to compare" — so the two agree about
|
|
30
|
+
which four exist, which axis each is measured from, and which two are exact. Two tables of one
|
|
31
|
+
fact is the shape this repository keeps finding wrong; their orders differ by design, so the sets
|
|
32
|
+
are what have to match.
|
|
33
|
+
- The "exact" column is a claim about arithmetic rather than a label, and it is now executed: it is
|
|
34
|
+
why `filterAnnotationsByTime` compares ticks, and the page warns that comparing the seconds
|
|
35
|
+
fields means "an onset and a bound that should be equal need not compare equal". Three tenths is
|
|
36
|
+
three times one tenth to the tick and not in seconds, on the rebased axis a window is measured
|
|
37
|
+
on.
|
|
38
|
+
- The worked example's four values are produced from a file built to its description, and the two
|
|
39
|
+
axes are checked to differ by exactly `timeline.startOffsetSeconds` — which is the whole reason
|
|
40
|
+
there are two of them.
|
|
41
|
+
|
|
9
42
|
## 0.4.372
|
|
10
43
|
|
|
11
44
|
- **Added** checks for the sample-grid section of `api-helpers.md`. The page opens by naming what a
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED