edfcore 0.4.409 → 0.4.411
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 +35 -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.411";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,41 @@ 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.411
|
|
10
|
+
|
|
11
|
+
- **Added** tests for the envelope of the files and selections a viewer produces by accident.
|
|
12
|
+
`readEnvelope` exists to draw a recording at pixel width, so its caller is a UI: the signal
|
|
13
|
+
indices come from a multi-select, the bucket count from a canvas width, and the file from
|
|
14
|
+
whatever was dropped on the page.
|
|
15
|
+
- **The same signal asked for twice** — a multi-select that appends on click, a "select all" over a
|
|
16
|
+
list that already had one checked — is now pinned as one series in order of first mention, and
|
|
17
|
+
costing what asking once costs. **A signal with no samples in a record** draws as an empty series
|
|
18
|
+
rather than failing the whole envelope, so a "plot everything" loop still gets a slot for every
|
|
19
|
+
channel it named. **A file whose records do not advance in time** buckets without dividing by the
|
|
20
|
+
duration: `readEnvelope` divides the samples evenly, because there are no timestamps to place
|
|
21
|
+
them along, and `readEnvelopeAtResolution` gets one bucket, because the span is zero.
|
|
22
|
+
- A fourth case is a request rather than a file: a `secondsPerBucket` finer than one tick has no
|
|
23
|
+
whole-tick answer, and asking for one bucket per tick and letting the fold clamp to one bucket per
|
|
24
|
+
sample was a comment with nothing behind it.
|
|
25
|
+
|
|
26
|
+
## 0.4.410
|
|
27
|
+
|
|
28
|
+
- **Added** a check that nothing on the site tells a crawler to stay away. `robots.txt.ts` opens
|
|
29
|
+
with a decision and its reasoning — everything is open to every crawler, including the AI
|
|
30
|
+
training crawlers, because an open-source library wants the opposite of what a publisher
|
|
31
|
+
protecting paid content wants — and that decision was enforced by nothing.
|
|
32
|
+
- Every way of reversing it is a normal-looking edit no reviewer would flag as a policy change: a
|
|
33
|
+
`Disallow:` added during a "block the AI scrapers" tidy-up; `Google-Extended` or
|
|
34
|
+
`Applebot-Extended` added to look thorough, whose only effect is to opt out of model training; a
|
|
35
|
+
`<meta name="robots" content="noindex">` copied from a staging site; an `X-Robots-Tag` in
|
|
36
|
+
`vercel.json`, which overrides the page and the file both. None changes anything a visitor sees.
|
|
37
|
+
- `check-site-output.mjs` reads the built `robots.txt` and checks one thing — that the sitemap it
|
|
38
|
+
names was emitted — and runs in CI only. This is the source-level half, in `npm run check`.
|
|
39
|
+
- The emitted lines are read out of the `body` array rather than the whole file. Scanning the file
|
|
40
|
+
for quoted strings does not work: the docblock is English, and one apostrophe in "a model's
|
|
41
|
+
training data" shifts the pairing for everything after it — which is how a `Disallow` line added
|
|
42
|
+
to the body went unseen while this check was being written.
|
|
43
|
+
|
|
9
44
|
## 0.4.409
|
|
10
45
|
|
|
11
46
|
- **Added** tests for the start offset a chunk has to derive when it does not begin at record 0.
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED