edf2csv 0.6.46 → 0.6.48
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 +27 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,33 @@
|
|
|
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.48
|
|
7
|
+
|
|
8
|
+
### Fixed: nothing said the JSON drops the hint every terminal warning carries
|
|
9
|
+
|
|
10
|
+
A warning on screen is two lines: the message, and an indented hint saying what to do. The
|
|
11
|
+
`warnings` array and `metadata.json`'s `notes` carry `code`, `severity` and `message` — and every
|
|
12
|
+
transcript on the site shows both lines, so a reader moving from the terminal to a script has no
|
|
13
|
+
reason to expect the second one to be gone.
|
|
14
|
+
|
|
15
|
+
Nothing on any page was false about this; it was absent, which for a machine-readable contract
|
|
16
|
+
is the same problem. Said outright now, with the reason — a hint varies with the run while a
|
|
17
|
+
code does not — and a pointer to where the remedy lives.
|
|
18
|
+
|
|
19
|
+
## 0.6.47
|
|
20
|
+
|
|
21
|
+
### Fixed: `INPUT_CHANGED` missing from the list of warnings `--info` cannot raise
|
|
22
|
+
|
|
23
|
+
It is raised in exactly two places, both inside `convert()`, and `--info` reaches neither. The
|
|
24
|
+
page lists four things a conversion can report that `--info` cannot and this was a fifth.
|
|
25
|
+
|
|
26
|
+
The guard behind that list cannot catch it. It converts every fixture, compares the codes
|
|
27
|
+
against `--info`'s, and requires any difference to be named on the page — and `INPUT_CHANGED`
|
|
28
|
+
fires only when a file moves mid-conversion, which a static fixture never does. So the sweep sees
|
|
29
|
+
the code on neither side and has nothing to compare. Same shape as 0.6.25, where the code was
|
|
30
|
+
missing a section: guards that compare observed behaviour are blind to what never happens in the
|
|
31
|
+
fixture set.
|
|
32
|
+
|
|
6
33
|
## 0.6.46
|
|
7
34
|
|
|
8
35
|
### Fixed: `--info --json` had no field reference, and was described as "the same fields"
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.48",
|
|
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",
|