edfcore 0.4.267 → 0.4.269
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 +27 -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.269";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,33 @@ 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.269
|
|
10
|
+
|
|
11
|
+
- **Corrected** what `documented-examples.test-d.ts` claims to be. It opened by saying its five
|
|
12
|
+
hand-written twins are the documented examples that get compiled, "deliberately small rather
|
|
13
|
+
than derived" — true when it was written and not since 0.4.263, which compiles all 102 fenced
|
|
14
|
+
blocks on the site in one pass. Leaving that sentence would be the defect this repository keeps
|
|
15
|
+
finding: a file describing itself as the coverage after something else became the coverage.
|
|
16
|
+
- It still earns its place, for one fence and a reason worth stating. The sweep judges a block by
|
|
17
|
+
compiling it alone, so a block that is a function body shown without its signature reports
|
|
18
|
+
`TS1108` and gets set aside — the `edfErrorKind` switch on `api-errors.md` is written that way,
|
|
19
|
+
and the hand-written twin is its only compilation. That is now asserted rather than described:
|
|
20
|
+
the snippet must contain a bare `return` and no function signature, so rewriting it as a whole
|
|
21
|
+
function fails here and prompts a reread of the division of labour instead of silently making
|
|
22
|
+
half this file redundant.
|
|
23
|
+
|
|
24
|
+
## 0.4.268
|
|
25
|
+
|
|
26
|
+
- **Added** a check that every `npm run …` in the documentation is a script that exists.
|
|
27
|
+
`AGENTS.md` opens with a Commands block, the README explains how to build the site, and
|
|
28
|
+
`tests/README.md` covers `test:scratch` — none of it verified, and scripts here do move:
|
|
29
|
+
`format` was rewritten in 0.4.225, `verify:package` added in 0.4.233, `lint` reshaped in
|
|
30
|
+
0.4.210. A stale one is a bad first minute for a contributor, because `npm run` on a missing
|
|
31
|
+
script prints an error and a list, which reads as a broken checkout rather than a stale page.
|
|
32
|
+
- `--prefix website` is followed rather than ignored. The two manifests have different scripts and
|
|
33
|
+
`npm run build` means a different thing in each, so the prefix genuinely changes the answer —
|
|
34
|
+
`dev` exists only in the site's.
|
|
35
|
+
|
|
9
36
|
## 0.4.267
|
|
10
37
|
|
|
11
38
|
- **Added** a check that the column table on the CLI page is the order `edfcore signals` emits.
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED