edfcore 0.4.324 → 0.4.326
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.326";
|
|
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.326
|
|
10
|
+
|
|
11
|
+
- **Added** the last unchecked section of `physical-values.md`: the four conditions that leave a
|
|
12
|
+
signal with no scale. Each row's code is produced by building the signal the row describes and
|
|
13
|
+
catching what `toPhysical` refuses it with, and the table's introduction — "checked in this
|
|
14
|
+
order" — is exercised against signals that trip two conditions at once, because the order is
|
|
15
|
+
what decides which code such a signal reports.
|
|
16
|
+
- The page's second verbatim message block is pinned the way 0.4.316 pinned the first: only the
|
|
17
|
+
hard wraps are undone, since the runs of spaces inside it are the raw eight-byte fields quoted as
|
|
18
|
+
the file holds them. Also checked is the asymmetry the section turns on — an inverted physical
|
|
19
|
+
range keeps its scale, because a negative amplifier gain has a documented meaning, and an
|
|
20
|
+
inverted digital range does not and is refused.
|
|
21
|
+
- With this, `edf-format.md` and `physical-values.md` are no longer the two pages nothing in the
|
|
22
|
+
suite reads.
|
|
23
|
+
|
|
24
|
+
## 0.4.325
|
|
25
|
+
|
|
26
|
+
- **Added** a check for the claim `edf-format.md` closes with: "Every diagnostic edfcore emits
|
|
27
|
+
names the clause it comes from." That is the promise that makes a warning adjudicable — `EDF+
|
|
28
|
+
additional specification 5` can be checked against a document — and nothing held it.
|
|
29
|
+
`specReference` is optional on `DiagnosticInit`, so leaving it out is neither a type error nor a
|
|
30
|
+
lint error, and most emission sites pass it positionally through a helper, which is why a static
|
|
31
|
+
scan of the object literals answers the wrong question.
|
|
32
|
+
- So the diagnostics are asked instead: nine targeted files for the header defects that need a
|
|
33
|
+
particular pair of fields, plus a bit-flip sweep over the first 900 bytes of a well-formed EDF+
|
|
34
|
+
file. Between them they produce twenty-four of the forty-six codes, every one of which names a
|
|
35
|
+
document rather than a feeling. The reach is asserted rather than assumed, and the docblock says
|
|
36
|
+
plainly that this demonstrates the claim over half the table rather than proving it over all of
|
|
37
|
+
it — the other twenty-two need conditions one fixture cannot reach.
|
|
38
|
+
|
|
9
39
|
## 0.4.324
|
|
10
40
|
|
|
11
41
|
- **Added** an execution of the TAL grammar `edf-format.md` prints as ABNF. Two of its five lines
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED