edf2csv 0.4.67 → 0.4.69

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/CHANGELOG.md +31 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -3,6 +3,37 @@
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.4.69
7
+
8
+ ### Added: `formatWallClock` is documented, and every export is checked to be
9
+
10
+ It was exported and mentioned nowhere, which matters more than a missing line. It is the
11
+ function that writes a recording's start time without a timezone, and the trap it exists to
12
+ avoid is one a caller falls into precisely because they did not know there was an
13
+ alternative: `startDateTime` is a UTC `Date` carrying the file's wall-clock digits so they
14
+ round-trip unshifted, and `toISOString()` on it appends a `Z` that asserts UTC. A reader
15
+ converting that to local time moves the recording by their own offset — 13:43:04 in the file
16
+ becomes 08:43:04 in New York.
17
+
18
+ A test now compares every name `dist/index.js` exports against api.md. Twenty-eight exports,
19
+ one of them undocumented, and nothing had been reading the list.
20
+
21
+ ## 0.4.68
22
+
23
+ ### Fixed: the landing page showed a timezone the format does not have
24
+
25
+ Its `--info` block read `Recorded 2002-03-02 23:10:00 UTC`. The tool prints no timezone,
26
+ deliberately — EDF stores local wall-clock digits and no zone at all, which is why the
27
+ metadata key is `start_datetime_local` and why the reader keeps `startDateRaw` beside the
28
+ parsed instant. A UTC suffix on the page arguing the tool is careful about exactly that was
29
+ the worst place to put one.
30
+
31
+ The comment above the block says every terminal and CSV sample on the page is real output
32
+ and nothing is a mock-up. Two of the three CSV samples had drifted from any recording that
33
+ exists, so the claim was half true. The recording is now described in that comment — five
34
+ signals plus annotations, 28800 records, the rates and ranges — and every block on the page
35
+ is the output of running the tool against it, regenerable by anyone who reads the recipe.
36
+
6
37
  ## 0.4.67
7
38
 
8
39
  ### Fixed: a documentation link pointed at a page the site does not serve
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "edf2csv",
3
- "version": "0.4.67",
3
+ "version": "0.4.69",
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",