edf2csv 0.6.42 → 0.6.43
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/docs/CHANGELOG.md +13 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,19 @@
|
|
|
3
3
|
Notable changes to edf2csv. Versions follow [semantic versioning](https://semver.org); while the
|
|
4
4
|
major version is 0, a minor bump may contain breaking changes.
|
|
5
5
|
|
|
6
|
+
## 0.6.43
|
|
7
|
+
|
|
8
|
+
### Fixed: `exceeds_spreadsheet_limit` was emitted by `--info --json` and documented nowhere
|
|
9
|
+
|
|
10
|
+
Thirty-one snake_case keys are written into the JSON this tool produces — the conversion
|
|
11
|
+
summary, the `--info` document and `metadata.json` — and thirty of them appear somewhere on the
|
|
12
|
+
site. This was the one that did not, on any page, in any form.
|
|
13
|
+
|
|
14
|
+
It is the machine-readable half of `LARGE_OUTPUT`: a boolean a script can branch on instead of
|
|
15
|
+
matching a warning message, which is exactly what the surrounding paragraphs tell scripts to do.
|
|
16
|
+
Its two siblings in the same object, `rows` and `bytes`, are documented a line away, including
|
|
17
|
+
0.6.0's rule about them being `null` when no signal table is written.
|
|
18
|
+
|
|
6
19
|
## 0.6.42
|
|
7
20
|
|
|
8
21
|
### Fixed: the `OUTPUT_UNWRITABLE` list of translated failures, stale since 0.6.11
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.43",
|
|
4
4
|
"description": "Convert EDF, EDF+ and BDF biosignal recordings (European Data Format) to CSV from the command line. Local, streaming, and never resamples or alters units.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"edf",
|