edfcore 0.4.495 → 0.4.496

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.
@@ -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.495";
112
+ export declare const VERSION = "0.4.496";
113
113
  //# sourceMappingURL=constants.d.ts.map
package/dist/constants.js CHANGED
@@ -79,5 +79,5 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
79
79
  reserved: 224,
80
80
  };
81
81
  /** Published package version. Kept in sync with package.json by a test. */
82
- export const VERSION = '0.4.495';
82
+ export const VERSION = '0.4.496';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,22 @@ 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.496
10
+
11
+ - **Added** a test that builds and runs the file `api-types.md` documents itself with. That page
12
+ explains the type surface by showing one recording's values — a six-record EDF+D with a gap,
13
+ 2,328 bytes — across nine separate snippets, and between them they state a byte offset, a byte
14
+ length, a tick count, a seconds-since-midnight, a sample count and what `locate` returns on both
15
+ sides of the gap. None of it had been run.
16
+ - `type-tables.test.ts` checks the TABLES on that page: every field a row lists exists on the type,
17
+ with the type it claims. The snippets between the tables are the other half, and they are where
18
+ the numbers are. A reader who wants to know what `chunk.byteOffset` means reads `1548`, not the
19
+ row that says `number`.
20
+ - Nine snippets and one file is what makes it worth building once. The page's internal consistency
21
+ is itself a claim — `1548` is `768 + 3 * 260`, and each of those three numbers is printed
22
+ elsewhere on the same page — so the fixture checks the arithmetic BETWEEN the snippets as well as
23
+ each snippet against the library. Every value is read out of the page.
24
+
9
25
  ## 0.4.495
10
26
 
11
27
  - **Added** a test that measures the two cost tables on `large-files.md`. That page is the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.495",
3
+ "version": "0.4.496",
4
4
  "description": "Modern, typed, zero-dependency reader for EDF, EDF+, BDF and BDF+ biosignal files. Works in browsers and Node with true random access.",
5
5
  "keywords": [
6
6
  "edf",
package/src/constants.ts CHANGED
@@ -93,4 +93,4 @@ export const SIGNAL_FIELD_BLOCK_OFFSETS = {
93
93
  } as const;
94
94
 
95
95
  /** Published package version. Kept in sync with package.json by a test. */
96
- export const VERSION = '0.4.495';
96
+ export const VERSION = '0.4.496';