edf2csv 0.6.54 → 0.6.55

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.
Files changed (2) hide show
  1. package/docs/CHANGELOG.md +17 -0
  2. package/package.json +1 -1
package/docs/CHANGELOG.md CHANGED
@@ -3,6 +3,23 @@
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.55
7
+
8
+ ### Fixed: the API reference's first example serialised `startDateTime` the one way it must not
9
+
10
+ ```js
11
+ console.log(`start ${file.header.startDateTime?.toISOString() ?? 'unknown'}`);
12
+ ```
13
+
14
+ That is the opening worked example on the page, and `toISOString()` is precisely what the same
15
+ page warns against six hundred lines later, in the paragraph explaining why `formatWallClock`
16
+ exists: the `Z` asserts UTC over digits the format never assigned a zone to, so a reader
17
+ converting to local time moves the recording by their own offset — "13:43:04 in the file becomes
18
+ 08:43:04 in New York".
19
+
20
+ The `EdfHeader` field list called it "a UTC `Date`" flatly, which is the belief that produces the
21
+ mistake. Both now say what the source comment says, and the example uses `formatWallClock`.
22
+
6
23
  ## 0.6.54
7
24
 
8
25
  ### 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.54",
3
+ "version": "0.6.55",
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",