edfcore 0.4.266 → 0.4.268
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 +26 -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.268";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,32 @@ 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.268
|
|
10
|
+
|
|
11
|
+
- **Added** a check that every `npm run …` in the documentation is a script that exists.
|
|
12
|
+
`AGENTS.md` opens with a Commands block, the README explains how to build the site, and
|
|
13
|
+
`tests/README.md` covers `test:scratch` — none of it verified, and scripts here do move:
|
|
14
|
+
`format` was rewritten in 0.4.225, `verify:package` added in 0.4.233, `lint` reshaped in
|
|
15
|
+
0.4.210. A stale one is a bad first minute for a contributor, because `npm run` on a missing
|
|
16
|
+
script prints an error and a list, which reads as a broken checkout rather than a stale page.
|
|
17
|
+
- `--prefix website` is followed rather than ignored. The two manifests have different scripts and
|
|
18
|
+
`npm run build` means a different thing in each, so the prefix genuinely changes the answer —
|
|
19
|
+
`dev` exists only in the site's.
|
|
20
|
+
|
|
21
|
+
## 0.4.267
|
|
22
|
+
|
|
23
|
+
- **Added** a check that the column table on the CLI page is the order `edfcore signals` emits.
|
|
24
|
+
That command exists to be piped into `awk`, so its columns are a positional contract, and two
|
|
25
|
+
places stated it: the table on `cli.md`, and `cli.test.ts`, which pinned it against a hard-coded
|
|
26
|
+
array. Neither knew about the other, so a column inserted rather than appended could be made to
|
|
27
|
+
pass by editing the test while the page went on describing the old layout to everyone parsing
|
|
28
|
+
it. Not hypothetical: column 6 was appended in 0.2.42 precisely so nothing reading the first
|
|
29
|
+
five by position would move, and before that the page claimed the command emitted samples per
|
|
30
|
+
record where it emitted `kind`, with the authoritative field in no column at all.
|
|
31
|
+
- The expectation is read from the page, and the fixture gives every column a distinct value — a
|
|
32
|
+
two-second record of fifty samples, so the rate is 25 and the count is 50 — because two columns
|
|
33
|
+
holding the same number would let a transposition through.
|
|
34
|
+
|
|
9
35
|
## 0.4.266
|
|
10
36
|
|
|
11
37
|
- **Added** a check that every `npx edfcore …` written in the documentation is one the CLI
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED