edfcore 0.4.258 → 0.4.259
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 +17 -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.259";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,23 @@ 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.259
|
|
10
|
+
|
|
11
|
+
- **Fixed** the snippet in `AGENTS.md` that does not compile. Its "Using edfcore in generated
|
|
12
|
+
code" section exists to be copied verbatim into somebody's project, which makes it the
|
|
13
|
+
highest-leverage code in the repository — and it ended `chunks[0].signals[0].digital`, which
|
|
14
|
+
under `noUncheckedIndexedAccess` is two `error TS2532`s, because both index reads are
|
|
15
|
+
`T | undefined`. That flag is on in this repo and in every strict TypeScript project, so the
|
|
16
|
+
file agents are told to copy from was teaching a line the compiler rejects. It narrows now,
|
|
17
|
+
which is what 0.4.208 settled on for this codebase over a `!`, and the two guards double as the
|
|
18
|
+
lesson the list right below it already gives: `readWindow` returns an array, and an empty one is
|
|
19
|
+
an ordinary answer.
|
|
20
|
+
- **Added** the compiled twin. `documented-examples.test-d.ts` has done this for three website
|
|
21
|
+
snippets since 0.3.46 found two of them rejected the same way; the snippet an agent is likeliest
|
|
22
|
+
to paste had no such guard. It runs both directions — the copy is real code `npm run typecheck`
|
|
23
|
+
compiles, and the test reads the fenced block back out of `AGENTS.md` and fails if a line of it
|
|
24
|
+
is missing here.
|
|
25
|
+
|
|
9
26
|
## 0.4.258
|
|
10
27
|
|
|
11
28
|
- **Added** a check on the `Next:` convention, which `AGENTS.md` states as an absolute — "every
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED