edf2csv 0.6.54 → 0.6.56
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 +30 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,36 @@
|
|
|
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.56
|
|
7
|
+
|
|
8
|
+
### Fixed: the `UNREADABLE` case list, four of the six things it covers
|
|
9
|
+
|
|
10
|
+
The reference gave a missing file, a directory where a file was expected, a permission failure
|
|
11
|
+
and a file that changed size mid-read. Missing: a path running through a regular file, which
|
|
12
|
+
0.6.12 taught the reader to word as "part of the path is a file, not a directory"; anything that
|
|
13
|
+
is not a regular file, such as a socket or a fifo; and calling a method on a closed `EdfFile`,
|
|
14
|
+
which is where a library caller meets this code most often.
|
|
15
|
+
|
|
16
|
+
Third time a message change in this line has left prose behind it, after 0.6.20 and 0.6.42 — and
|
|
17
|
+
the same remedy each time: diff the list against the function, don't read it.
|
|
18
|
+
|
|
19
|
+
## 0.6.55
|
|
20
|
+
|
|
21
|
+
### Fixed: the API reference's first example serialised `startDateTime` the one way it must not
|
|
22
|
+
|
|
23
|
+
```js
|
|
24
|
+
console.log(`start ${file.header.startDateTime?.toISOString() ?? 'unknown'}`);
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
That is the opening worked example on the page, and `toISOString()` is precisely what the same
|
|
28
|
+
page warns against six hundred lines later, in the paragraph explaining why `formatWallClock`
|
|
29
|
+
exists: the `Z` asserts UTC over digits the format never assigned a zone to, so a reader
|
|
30
|
+
converting to local time moves the recording by their own offset — "13:43:04 in the file becomes
|
|
31
|
+
08:43:04 in New York".
|
|
32
|
+
|
|
33
|
+
The `EdfHeader` field list called it "a UTC `Date`" flatly, which is the belief that produces the
|
|
34
|
+
mistake. Both now say what the source comment says, and the example uses `formatWallClock`.
|
|
35
|
+
|
|
6
36
|
## 0.6.54
|
|
7
37
|
|
|
8
38
|
### Fixed: the FAQ's truncation transcript punctuated the hint differently from the tool
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.56",
|
|
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",
|