edfcore 0.4.269 → 0.4.271
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 +31 -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.271";
|
|
113
113
|
//# sourceMappingURL=constants.d.ts.map
|
package/dist/constants.js
CHANGED
package/docs/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,37 @@ 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.271
|
|
10
|
+
|
|
11
|
+
- **Added** the check the whole suite rests on: nothing in `tests/support/` takes a runtime import
|
|
12
|
+
from `src/`. `tests/README.md` states it twice — "a reader and a writer that share a
|
|
13
|
+
misunderstanding agree with each other and are wrong together" — and nothing enforced it.
|
|
14
|
+
Ninety test files build their fixtures with that writer. Had it taken `EDF_HEADER_BLOCK_BYTES`
|
|
15
|
+
from `src/constants.ts`, which looks exactly like sensible de-duplication and is one line, a
|
|
16
|
+
wrong constant would have produced fixtures shaped to match the wrong reader and two thousand
|
|
17
|
+
tests would have passed on a broken package, proving only that edfcore agrees with itself. That
|
|
18
|
+
is the one failure a suite cannot see from the inside.
|
|
19
|
+
- Walked transitively, because independence one import deep is not independence — a helper
|
|
20
|
+
importing both the writer and a `src/` constant would launder precisely what this forbids, and
|
|
21
|
+
the check was verified against that shape as well as the direct one. `import type` is exempt on
|
|
22
|
+
the same reasoning 0.4.256 used: `spy-source.ts` has to name the `ByteSource` it wraps, and
|
|
23
|
+
naming a shape is not sharing an understanding of the bytes.
|
|
24
|
+
|
|
25
|
+
## 0.4.270
|
|
26
|
+
|
|
27
|
+
- **Added** a check that every file this repository names in a comment is a file that is there.
|
|
28
|
+
Docblocks here point at each other constantly — `header/parse.ts` owns validation order,
|
|
29
|
+
`tal/ticks.ts` owns the tick conversion — and 324 of those references are written as backticked
|
|
30
|
+
paths that nothing reads. The `src/` half matters most: `removeComments: false` copies those
|
|
31
|
+
docblocks into `dist/*.d.ts`, so a path that stopped existing ships to every consumer as hover
|
|
32
|
+
text. Not hypothetical — `CHANGELOG.md` became `docs/CHANGELOG.md` at v0.4.1, and 0.4.264
|
|
33
|
+
renamed a test file when its rule outgrew its name.
|
|
34
|
+
- **Reworded** two comments that named things which were never files: a hypothetical
|
|
35
|
+
`guides/whatever.md` and the served route `api.json`, where the file is `api.json.ts`. Both
|
|
36
|
+
would have needed an exemption, and an exemption for "paths that are not paths" is how a check
|
|
37
|
+
stops meaning anything. `dist/` is the one that remains, because the build output is described
|
|
38
|
+
in several places and committed in none.
|
|
39
|
+
|
|
9
40
|
## 0.4.269
|
|
10
41
|
|
|
11
42
|
- **Corrected** what `documented-examples.test-d.ts` claims to be. It opened by saying its five
|
package/package.json
CHANGED
package/src/constants.ts
CHANGED