edfcore 0.4.485 → 0.4.486
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 +14 -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.486";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,20 @@ 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.486
|
|
10
|
+
|
|
11
|
+
- **Added** tests for the sentence the repeat counter turns into. `parseTalRegion` collapses many
|
|
12
|
+
occurrences of one defect into a single issue carrying a count, and `grammar.test.ts` pins the
|
|
13
|
+
counter thoroughly — but nothing checked whether the clause `reportIssue` builds from it appears
|
|
14
|
+
when it should and stays away when it should not.
|
|
15
|
+
- Relaxing that guard puts "(1 occurrences in this region; the first is described)" on the
|
|
16
|
+
ordinary case. Ungrammatical, and worse than ungrammatical: it tells a reader looking at a
|
|
17
|
+
single bad TAL that there are others they cannot see. The same defect 0.4.421 fixed on the
|
|
18
|
+
validation report's first line — a count rendered without asking whether it needed rendering.
|
|
19
|
+
- Both directions and the threshold: one occurrence carries no count, two says two, three says
|
|
20
|
+
three, and the bytes quoted are the FIRST offender's, which is what the clause promises. The
|
|
21
|
+
two-occurrence case is what stops a guard reading `> 2` passing everything else.
|
|
22
|
+
|
|
9
23
|
## 0.4.485
|
|
10
24
|
|
|
11
25
|
- **Added** the edge cases for the sub-second start offset, which is documented as `[0, 1)` and
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED