edfcore 0.4.506 → 0.4.507

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.506";
112
+ export declare const VERSION = "0.4.507";
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.506';
82
+ export const VERSION = '0.4.507';
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.507
10
+
11
+ - **Added** a property test that `readWindow` and `readRecords` agree. They are the two selections
12
+ the API offers — name a time, or name records — and on a contiguous file a window landing on
13
+ record boundaries selects exactly the records a caller would have named, so the two must produce
14
+ the same bytes, sample counts, start and `byteOffset`. Nothing compared them.
15
+ - That is the failure this project has hit repeatedly and names in `whole-api.test.ts`: "a function
16
+ can be individually correct and still disagree with its neighbour — six releases of this project
17
+ were exactly that". Each call had its own tests; the pair had none.
18
+ - The window is derived from the records rather than typed, over arbitrary starts and counts and
19
+ three geometries, two of them with a record duration that is not a whole number of seconds.
20
+ `readWindow` resolves through `resolveTimeWindow` and `readRecords` does not, so the two reach
21
+ the same range by different arithmetic — which is the only reason comparing them means anything.
22
+ - The limit is asserted too: half a record in, the window is no longer aligned and `readWindow`
23
+ returns both records, because a record is the unit the file can be read by.
24
+
9
25
  ## 0.4.506
10
26
 
11
27
  - **Added** the four-row cost table on `validation.md`, and the claim it exists to support:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.506",
3
+ "version": "0.4.507",
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.506';
96
+ export const VERSION = '0.4.507';