edf2csv 0.6.17 → 0.6.18
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 +11 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,17 @@
|
|
|
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.18
|
|
7
|
+
|
|
8
|
+
### Fixed: the FAQ's exit codes, in the answer written for scripts
|
|
9
|
+
|
|
10
|
+
Third page with this gap, after the README in 0.6.10 and getting-started in 0.6.16, and the one
|
|
11
|
+
where it costs most: the question is "how do I check whether a conversion had problems from a
|
|
12
|
+
script", and the answer gave three codes as the whole set. A pipeline built on it reads 1 as "a
|
|
13
|
+
problem with the file or the output directory" — but the same page recommends `--strict` two
|
|
14
|
+
sections later, and `--strict` returns 1 over a conversion that wrote every file it meant to.
|
|
15
|
+
130 was missing as well.
|
|
16
|
+
|
|
6
17
|
## 0.6.17
|
|
7
18
|
|
|
8
19
|
### Fixed: the list of what writes to stdout left out `--stdout`
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.18",
|
|
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",
|