edfcore 0.4.178 → 0.4.180

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/dist/cli-run.js CHANGED
@@ -50,7 +50,7 @@ Options
50
50
  --patient include patient identification (header, validate, json)
51
51
  --list list events one per line instead of counting (events)
52
52
  --limit <n> diagnostics or events to print, default 20
53
- (header, validate, events)
53
+ (header, validate, events --list)
54
54
  --version, -v print the version and exit
55
55
 
56
56
  Exit codes: 0 success, 1 the file is unreadable or failed validation, 2 bad usage.
@@ -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.178";
112
+ export declare const VERSION = "0.4.180";
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.178';
82
+ export const VERSION = '0.4.180';
83
83
  //# sourceMappingURL=constants.js.map
package/docs/CHANGELOG.md CHANGED
@@ -6,6 +6,17 @@ 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.180
10
+
11
+ - **Corrected** the same `--limit` scope on `api-helpers.md`, the other half of 0.4.179, and said
12
+ outright that the counted `events` output is never capped.
13
+
14
+ ## 0.4.179
15
+
16
+ - **Corrected** the `--limit` scope in `edfcore --help`. It said "(header, validate, events)", but
17
+ the counted `events` output ignores it entirely; only `events --list` is capped. 0.3.124 added the
18
+ scopes and this one was a command too broad.
19
+
9
20
  ## 0.4.178
10
21
 
11
22
  - **Fixed** `edfcore <command> <directory>` reporting a raw `EISDIR: illegal operation on a
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edfcore",
3
- "version": "0.4.178",
3
+ "version": "0.4.180",
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/cli-run.ts CHANGED
@@ -61,7 +61,7 @@ Options
61
61
  --patient include patient identification (header, validate, json)
62
62
  --list list events one per line instead of counting (events)
63
63
  --limit <n> diagnostics or events to print, default 20
64
- (header, validate, events)
64
+ (header, validate, events --list)
65
65
  --version, -v print the version and exit
66
66
 
67
67
  Exit codes: 0 success, 1 the file is unreadable or failed validation, 2 bad usage.
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.178';
96
+ export const VERSION = '0.4.180';