edfcore 0.4.248 → 0.4.250

package/dist/constants.d.ts

@@ -109,5 +109,5 @@ export declare const SIGNAL_FIELD_BLOCK_OFFSETS: {
     readonly reserved: 224;
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export declare const VERSION = "0.4.248";
+export declare const VERSION = "0.4.250";
 //# sourceMappingURL=constants.d.ts.map

package/dist/constants.js

@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
     reserved: 224,
 };
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.248';
+export const VERSION = '0.4.250';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,30 @@ alone does not tell you whether you were affected.
 edfcore is pre-1.0. Patch releases have carried behaviour changes where the old behaviour was a
 defect; those are called out below.
 
+## 0.4.250
+
+- **Documented the last one.** `EdfAnnotationWindow` is what `filterAnnotationsByTime` takes, and
+  `api-helpers.md` showed the object literal without naming the type or saying why it is not
+  `WindowSelection`: there is no reading here and so no channel to name, which makes it the one
+  window type in the package that never touches a `ByteSource`.
+- **Emptied** `UNDOCUMENTED_TYPES`. It held fourteen exported types when 0.4.220 wrote it down,
+  and six releases took them off — three formatter options, three selections, three envelope
+  results, two BioSemi, two summary, and this one. The title of `docs-coverage.test.ts` has been
+  qualified since 0.4.221 because it had to be; it is plain again. The empty set stays rather than
+  being deleted: it is the seam a future exception would go in, and while it holds nothing the
+  check above it is unconditional.
+
+## 0.4.249
+
+- **Added** documentation for the two diagnostic summary types, leaving one on the recorded
+  undocumented list. `diagnostics.md` showed `summary.total`, `summary.worst` and `summary.byCode`
+  field by field without naming `EdfDiagnosticSummary` or `EdfCodeCount`, which is exactly
+  backwards for this call: its whole purpose is to be handed to a renderer, and writing that
+  renderer means naming its parameter. Both now have a field table, including why `EdfCodeCount`
+  carries a severity of its own — so ranking codes never has to reach back into the diagnostics
+  array to find out whether the most frequent one is also the most serious, which it usually
+  is not.
+
 ## 0.4.248
 
 - **Added** documentation for the two BioSemi types, taking the recorded undocumented list from

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.248",
+  "version": "0.4.250",
   "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
   "keywords": [
     "edf",

package/src/constants.ts

@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
 } as const;
 
 /** Published package version. Kept in sync with package.json by a test. */
-export const VERSION = '0.4.248';
+export const VERSION = '0.4.250';