edfcore 0.6.50 → 0.6.51

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/README.md CHANGED
@@ -21,7 +21,7 @@ npx edfcore validate overnight.edf # full conformance sweep; exits 1 on f
21
21
  npx edfcore json overnight.edf # the header as JSON, for jq
22
22
  ```
23
23
 
24
- Patient identification is omitted unless you pass `--patient`. Diagnostics and events print twenty
24
+ Patient identification is omitted unless you pass `--patient`. Diagnostics, events and gaps print twenty
25
25
  at a time; `--limit <n>` changes that.
26
26
 
27
27
  ## How do I read an EDF file in JavaScript?
@@ -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.6.50";
112
+ export declare const VERSION = "0.6.51";
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.6.50';
82
+ export const VERSION = '0.6.51';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,18 @@ 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.6.51
10
+
11
+ - **Fixed** the README's account of what `--limit` caps. It said "Diagnostics and events print
12
+ twenty at a time", which was true until 0.6.29 brought `gaps` under the same cap. That release
13
+ updated the usage text and `cli.md` and left the README naming two of the three.
14
+ - `gaps` is the one it mattered for. It is the only listing bounded by nothing but the record
15
+ count — an ambulatory recorder that stops and restarts across a night produces hundreds of rows
16
+ — so a reader of the README believed the flag did not reach the command that most needs it.
17
+ - A test now reads the noun list out of the usage text and out of the README and compares them,
18
+ rather than restating the sentence. `cli-limit-default.test.ts` pins the number; this pins what
19
+ the number applies to.
20
+
9
21
  ## 0.6.50
10
22
 
11
23
  - **Changed** the message `--limit -1` earns. It said "`--limit` needs a whole number, received
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.6.50",
3
+ "version": "0.6.51",
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.6.50';
96
+ export const VERSION = '0.6.51';