edfcore 0.4.332 → 0.4.334

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.332";
+export declare const VERSION = "0.4.334";
 //# 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.332';
+export const VERSION = '0.4.334';
 //# sourceMappingURL=constants.js.map

package/docs/CHANGELOG.md

@@ -6,6 +6,34 @@ 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.334
+
+- **Added** a check over the `validateHeader` table on `api-validate.md`, which was one of the four
+  pages no test named. The table lists ten codes; the sentence under it does the real work, saying
+  four of them "exist nowhere else in edfcore" and that "the other six are also emitted by the
+  parser, so a report stands on its own instead of only making sense next to
+  `header.diagnostics`."
+- That claim rots silently in both directions. Moving one of the four into the parser makes a
+  validation report redundant for that code while the page still calls it exclusive; moving one of
+  the six out breaks the sentence the other way. Both halves are now settled by asking which
+  modules under `src/` name each code. Also checked: none of the ten is fatal, since a fatal code
+  here would let `validateHeader` condemn a file the parser opened without complaint, and the
+  fourteen label types the page spells out are read out of `STANDARD_LABEL_TYPES` in order.
+- `diagnostic-docs.test.ts` covers how severe a code is across every page. This is the narrower
+  question it does not ask: who is entitled to emit one.
+
+## 0.4.333
+
+- **Added** the rest of `migrating-to-0-3.md`: the difference the page calls structural. `sampleAt`
+  returns `undefined` for each of the three reasons the page gives — the instant falls in a gap,
+  before the recording, or after it — and returns a location either side of the hole, so that
+  `undefined` is a statement about the file rather than the function's usual answer.
+- The other half is that the grid form has no way to say it. Given only a signal and a record
+  duration it returns an index at every instant, including one past the end of the file, which is
+  checked against the record count. And both refuse a probed index on a file with gaps: the same
+  fixture throws before `buildRecordIndex` and answers after it, with `contiguityOf` reporting
+  `'unknown'` in between.
+
 ## 0.4.332
 
 - **Fixed** a test of mine that could time out. The UTF-8 sweep added in 0.4.324 encoded each of

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "edfcore",
-  "version": "0.4.332",
+  "version": "0.4.334",
   "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.332';
+export const VERSION = '0.4.334';