edf2csv 0.6.37 → 0.6.38
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 +14 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,20 @@
|
|
|
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.38
|
|
7
|
+
|
|
8
|
+
### Fixed: `INPUT_UNREADABLE` had no section, and is the one that leaves output behind
|
|
9
|
+
|
|
10
|
+
Second of the four undocumented `ConversionErrorCode` values. It is not a duplicate of
|
|
11
|
+
`UNREADABLE`: that one fails before anything is written, this one fails during the streaming
|
|
12
|
+
pass, so the difference between them is whether there is a half-finished directory on disk. The
|
|
13
|
+
code separates them for exactly that reason — a read failure used to be reported as
|
|
14
|
+
`Writing to "<dir>" failed` with advice about disk space, pointing at the part of the system
|
|
15
|
+
that was working.
|
|
16
|
+
|
|
17
|
+
The page had the distinction nowhere, so a reader hitting the second met a message whose code
|
|
18
|
+
they could not look up.
|
|
19
|
+
|
|
6
20
|
## 0.6.37
|
|
7
21
|
|
|
8
22
|
### Fixed: `INPUT_OUTPUT_COLLISION` had no section on the errors page
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.38",
|
|
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",
|