edf2csv 0.6.87 → 0.6.89
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 +33 -0
- package/package.json +1 -1
package/docs/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,39 @@
|
|
|
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.89
|
|
7
|
+
|
|
8
|
+
### the pages knew their place in the sequence and never said so
|
|
9
|
+
|
|
10
|
+
Two places where the site knew something it never told the reader.
|
|
11
|
+
|
|
12
|
+
The documentation is an ordered set — the frontmatter carries an `order`, the sidebar is sorted by
|
|
13
|
+
it, the footer offers the next page, and the breadcrumb structured data has described the position
|
|
14
|
+
to crawlers since 0.6.62. Nothing said it to a person. Each page now opens with where it sits:
|
|
15
|
+
"Documentation / 4 of 11", which is what makes the previous/next pair read as a sequence rather
|
|
16
|
+
than as two arbitrary neighbours, and tells someone arriving from a search result how much of the
|
|
17
|
+
set they are standing in.
|
|
18
|
+
|
|
19
|
+
The Markdown mirrors gained the version, for the reason 0.6.83 gave the llms files one. A mirror is
|
|
20
|
+
fetched in order to be kept — pasted into a conversation, cached by an agent, saved next to a
|
|
21
|
+
script — and the HTML page it copies states its version in structured data while the copy stated
|
|
22
|
+
nothing at all.
|
|
23
|
+
|
|
24
|
+
## 0.6.88
|
|
25
|
+
|
|
26
|
+
### nothing checked that an anchor arrives where it says
|
|
27
|
+
|
|
28
|
+
The duplicate id fixed in 0.6.87 had been shipping for as long as both headings had existed, and it
|
|
29
|
+
survived every check this site has: it is valid-looking markup, it renders correctly, no link
|
|
30
|
+
404s, and the page reads properly top to bottom. The only symptom is that one link in the contents
|
|
31
|
+
list arrives at the wrong paragraph — which is exactly what proof-reading does not catch and what a
|
|
32
|
+
build can settle in a dozen lines.
|
|
33
|
+
|
|
34
|
+
Every emitted page is now checked for two things: no id used twice, and no `href="#..."` pointing
|
|
35
|
+
at an element that does not exist. Verified by breaking each one deliberately — removing the
|
|
36
|
+
numbering from the slugger, then misspelling a contents link — and confirming the build stops with
|
|
37
|
+
the page and the id named, before putting both back.
|
|
38
|
+
|
|
6
39
|
## 0.6.87
|
|
7
40
|
|
|
8
41
|
### two headings shared an id and the second link went to the first
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "edf2csv",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.89",
|
|
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",
|