edfcore 0.4.268 → 0.4.270
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 +30 -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.270";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,36 @@ 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.270
|
|
10
|
+
|
|
11
|
+
- **Added** a check that every file this repository names in a comment is a file that is there.
|
|
12
|
+
Docblocks here point at each other constantly — `header/parse.ts` owns validation order,
|
|
13
|
+
`tal/ticks.ts` owns the tick conversion — and 324 of those references are written as backticked
|
|
14
|
+
paths that nothing reads. The `src/` half matters most: `removeComments: false` copies those
|
|
15
|
+
docblocks into `dist/*.d.ts`, so a path that stopped existing ships to every consumer as hover
|
|
16
|
+
text. Not hypothetical — `CHANGELOG.md` became `docs/CHANGELOG.md` at v0.4.1, and 0.4.264
|
|
17
|
+
renamed a test file when its rule outgrew its name.
|
|
18
|
+
- **Reworded** two comments that named things which were never files: a hypothetical
|
|
19
|
+
`guides/whatever.md` and the served route `api.json`, where the file is `api.json.ts`. Both
|
|
20
|
+
would have needed an exemption, and an exemption for "paths that are not paths" is how a check
|
|
21
|
+
stops meaning anything. `dist/` is the one that remains, because the build output is described
|
|
22
|
+
in several places and committed in none.
|
|
23
|
+
|
|
24
|
+
## 0.4.269
|
|
25
|
+
|
|
26
|
+
- **Corrected** what `documented-examples.test-d.ts` claims to be. It opened by saying its five
|
|
27
|
+
hand-written twins are the documented examples that get compiled, "deliberately small rather
|
|
28
|
+
than derived" — true when it was written and not since 0.4.263, which compiles all 102 fenced
|
|
29
|
+
blocks on the site in one pass. Leaving that sentence would be the defect this repository keeps
|
|
30
|
+
finding: a file describing itself as the coverage after something else became the coverage.
|
|
31
|
+
- It still earns its place, for one fence and a reason worth stating. The sweep judges a block by
|
|
32
|
+
compiling it alone, so a block that is a function body shown without its signature reports
|
|
33
|
+
`TS1108` and gets set aside — the `edfErrorKind` switch on `api-errors.md` is written that way,
|
|
34
|
+
and the hand-written twin is its only compilation. That is now asserted rather than described:
|
|
35
|
+
the snippet must contain a bare `return` and no function signature, so rewriting it as a whole
|
|
36
|
+
function fails here and prompts a reread of the division of labour instead of silently making
|
|
37
|
+
half this file redundant.
|
|
38
|
+
|
|
9
39
|
## 0.4.268
|
|
10
40
|
|
|
11
41
|
- **Added** a check that every `npm run …` in the documentation is a script that exists.
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED