edfcore 0.4.378 → 0.4.380
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 +28 -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.380";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,34 @@ 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.380
|
|
10
|
+
|
|
11
|
+
- **Added** enforcement for the fixture policy in `tests/README.md`: "No file from teuniz.net,
|
|
12
|
+
PhysioNet or edfplus.info may be committed." That is a licence rule and a privacy one — one of
|
|
13
|
+
those files is a real person's overnight polysomnogram, and committing it would publish it to
|
|
14
|
+
npm's mirrors and to every fork, permanently, in a way no later commit can undo.
|
|
15
|
+
- It held by one line in `.gitignore` and by nobody adding an exception, which is the shape of rule
|
|
16
|
+
that survives until the day someone wants a test to run in CI. Now every file the corpus can
|
|
17
|
+
download is checked against what git tracks, the whole download directory is checked rather than
|
|
18
|
+
the manifest's filenames alone, and every manifest entry has to record its source and licence —
|
|
19
|
+
a file whose licence nobody wrote down is one nobody can decide about later.
|
|
20
|
+
- The committed exception is checked to be exactly what the README says it is: the only tracked
|
|
21
|
+
EDF, BDF or REC files are the six goldens, none of which shares a name with anything the manifest
|
|
22
|
+
fetches, because they were generated locally rather than downloaded from anyone.
|
|
23
|
+
|
|
24
|
+
## 0.4.379
|
|
25
|
+
|
|
26
|
+
- **Added** an execution of the "Oddities that bite implementers" section of `edf-format.md`, which
|
|
27
|
+
is that page's payload: seven paragraphs each naming a thing about EDF that produces a wrong
|
|
28
|
+
answer rather than an error. The page is written for someone about to write their own parser —
|
|
29
|
+
which the comparison page says is what people overwhelmingly do — so these are the claims most
|
|
30
|
+
likely to be acted on by a reader who never installs the package.
|
|
31
|
+
- Each is checked against the library, because that is the only way to check them and because each
|
|
32
|
+
is a place edfcore could regress into the naive behaviour being warned about. A date eighty years
|
|
33
|
+
wrong, a record count silently short, a rate of `Infinity`, a first header byte mangled by the
|
|
34
|
+
decoder that read it, and a redundant header size believed over the computed one — every
|
|
35
|
+
paragraph describes a bug that looks like working software.
|
|
36
|
+
|
|
9
37
|
## 0.4.378
|
|
10
38
|
|
|
11
39
|
- **Added** a check that the browser inspector uploads nothing, which is the most consequential
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED