Compare commits
1 Commits
v0.1.0
..
9e469df200
| Author | SHA1 | Date | |
|---|---|---|---|
| 9e469df200 |
Generated
+3
-3
@@ -1,19 +1,19 @@
|
|||||||
{
|
{
|
||||||
"name": "@larvit/adf-codec",
|
"name": "@larvit/adf-codec",
|
||||||
"version": "0.1.0",
|
"version": "0.0.0",
|
||||||
"lockfileVersion": 3,
|
"lockfileVersion": 3,
|
||||||
"requires": true,
|
"requires": true,
|
||||||
"packages": {
|
"packages": {
|
||||||
"": {
|
"": {
|
||||||
"name": "@larvit/adf-codec",
|
"name": "@larvit/adf-codec",
|
||||||
"version": "0.1.0",
|
"version": "0.0.0",
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"devDependencies": {
|
"devDependencies": {
|
||||||
"@types/node": "24.13.3",
|
"@types/node": "24.13.3",
|
||||||
"typescript": "7.0.2"
|
"typescript": "7.0.2"
|
||||||
},
|
},
|
||||||
"engines": {
|
"engines": {
|
||||||
"node": ">=18"
|
"node": ">=24"
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"node_modules/@types/node": {
|
"node_modules/@types/node": {
|
||||||
|
|||||||
+2
-1
@@ -1,6 +1,7 @@
|
|||||||
{
|
{
|
||||||
"name": "@larvit/adf-codec",
|
"name": "@larvit/adf-codec",
|
||||||
"version": "0.1.0",
|
"version": "0.0.0",
|
||||||
|
"private": true,
|
||||||
"description": "Lossless conversion between Atlassian Document Format, extended markdown and HTML",
|
"description": "Lossless conversion between Atlassian Document Format, extended markdown and HTML",
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"repository": {
|
"repository": {
|
||||||
|
|||||||
@@ -5,8 +5,8 @@ milestone. A done item shrinks to its title here; its full text moves to `todo-h
|
|||||||
|
|
||||||
## Milestones
|
## Milestones
|
||||||
|
|
||||||
Shipping order: 3h, 3i, 3j, 5a, 5b, 5c, 5d, 5 → `0.1.0`; 4b, 4c and 4d → `0.1.1`; 4, 3k → `0.2.0`;
|
Shipping order: 3h, 3i, 3j, 5a, 5b, 5c, 5d, 5 → `0.1.0`; 4b and 4c → `0.1.1`; 4, 3k → `0.2.0`;
|
||||||
6, 7 → `0.3.0`.
|
6, 7 → `0.3.0`; 9, 10, 11 → TBD.
|
||||||
The numbering is the order the work was planned in, not the order it ships.
|
The numbering is the order the work was planned in, not the order it ships.
|
||||||
|
|
||||||
- [x] **0 — Scaffold.**
|
- [x] **0 — Scaffold.**
|
||||||
@@ -112,20 +112,6 @@ The numbering is the order the work was planned in, not the order it ships.
|
|||||||
cost, which 3i's slot parse doubles rather than changes in class, bounded by the 500-level
|
cost, which 3i's slot parse doubles rather than changes in class, bounded by the 500-level
|
||||||
guard. §11's scanning rule is the whole argument; the pipeline persona feeds documents
|
guard. §11's scanning rule is the whole argument; the pipeline persona feeds documents
|
||||||
nobody typed.
|
nobody typed.
|
||||||
- [ ] **4d — What the gate says while it runs (`0.1.1`).** `ci.sh` runs nine legs and announces
|
|
||||||
none of them, so five minutes of a Gitea run read as silence and a hang cannot be told from
|
|
||||||
a slow pull — the maintainer hit exactly this on the `0.1.0` release. Three causes, each its
|
|
||||||
own fix. The legs need markers: `plainpages`' `ci.sh` prints a `step()` header per leg and
|
|
||||||
this one prints nothing, so name the leg and the image before each. The longest leg is the
|
|
||||||
quietest: `test_output=$(… npm test 2>&1)` buffers the whole Node run to replay it after,
|
|
||||||
because the zero-test guard greps the count — stream it and grep a copy (`tee`), rather than
|
|
||||||
trading the output for the guard. And two legs are silenced outright, `npm pack` and the
|
|
||||||
tarball install, whose `>/dev/null` predates the offline install that made them quick and
|
|
||||||
quiet. `publish.sh` owes the same: today it says nothing between reading `private` and the
|
|
||||||
registry answering, which is where its `npm ci` and rebuild sit — the seconds §9 accepts
|
|
||||||
rather than promoting the gate's `dist`, and unmeasured until the log shows them. Per-leg
|
|
||||||
timing is what turns "slow or hung" from a guess into a reading; the browser leg's own
|
|
||||||
5.4–7.9s against a 17s warm gate is the number that made it obviously cheap.
|
|
||||||
- [ ] **5 — Ship `0.1.0`.** Only the maintainer's own acts are left (§15): make the Gitea repo
|
- [ ] **5 — Ship `0.1.0`.** Only the maintainer's own acts are left (§15): make the Gitea repo
|
||||||
public (§6), create the `NPM_TOKEN` secret, confirm the Actions token may push tags — the
|
public (§6), create the `NPM_TOKEN` secret, confirm the Actions token may push tags — the
|
||||||
publish succeeds and the tag push then reddens the run, though the next push to `main`
|
publish succeeds and the tag push then reddens the run, though the next push to `main`
|
||||||
@@ -152,6 +138,9 @@ The numbering is the order the work was planned in, not the order it ships.
|
|||||||
- [ ] **7 — HTML, ship `0.3.0`.** `adfToHtml`, `htmlToAdf`, the composed `markdownToHtml` /
|
- [ ] **7 — HTML, ship `0.3.0`.** `adfToHtml`, `htmlToAdf`, the composed `markdownToHtml` /
|
||||||
`htmlToMarkdown`. CommonMark spec suite runs against `markdownToHtml` from here (§10).
|
`htmlToMarkdown`. CommonMark spec suite runs against `markdownToHtml` from here (§10).
|
||||||
- [ ] **8 — CLI.** A later goal, shaped around the personas once the library exists.
|
- [ ] **8 — CLI.** A later goal, shaped around the personas once the library exists.
|
||||||
|
- [ ] **9 — The online sandbox.** A web page with two textboxes converting back and forth between ADF and markdown, powered by the library's browser build.
|
||||||
|
- [ ] **10 — Lossy conversion.** A direction that only converts what Markdown supports. Data from the ADF is preserved but format, design and other non-markdown constructs are dropped.
|
||||||
|
- [ ] **11 — Evaluate `@atlaskit/adf-schema`.** Determine whether `@atlaskit/adf-schema` should be added as a dev dependency to serve as truth for the ADF schema.
|
||||||
|
|
||||||
## The ADF inventory to cover
|
## The ADF inventory to cover
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user