lilleman
|
770cc3b938
|
Compare the package with the other ADF converters in the README
|
2026-10-14 20:15:39 +02:00 |
|
lilleman
|
6c389b9c83
|
Answer prose round 1: 0 🔴, 8 🟡; say which marks a node refuses, and name the fix in the directive mark refusal
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
bb3a128233
|
Answer product-owner round 1: 0 🔴, 1 🟡; name the refusal stored markdown meets, and make the next release 0.3.0
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
6842f386ae
|
Answer architecture round 1: 2 🔴, 4 🟡; refuse a link around only nodes that take none, mark the change breaking, file code-text marks
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
1ae7ba6992
|
Give an inline node no mark Atlassian's schema withholds from it, in every reader
|
2026-10-14 15:08:46 +02:00 |
|
lilleman
|
dd8dabc9e8
|
Answer product-owner round 1: 0 🔴, 1 🟡; drop the optional link title from the linked-image hint
|
2026-10-14 13:18:14 +02:00 |
|
lilleman
|
3391154518
|
Name the CommonMark spelling a refused directive takes, split the unsupported-node-shape row by cause, and pass readAttributes its pair fault
|
2026-10-14 13:18:14 +02:00 |
|
lilleman
|
f73b5c4f76
|
Release 0.2.0
|
2026-10-14 11:58:21 +02:00 |
|
lilleman
|
70be4049a3
|
Answer CodeRabbit round 1: 0 🔴, 1 🟡; the changelog refuses only an array the new spelling holds
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
aefcd4b9e3
|
Answer prose round 1: 0 🔴, 6 🟡; the changelog names what breaks, the fallback reads as untyped mark, attribute or value, the spec's value list and marks paragraph split, messages name the JSON array to write
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
168ca1cea2
|
Answer stability round 1: 0 🔴, 2 🟡; a mark's malformed attrs name their cause, the docs name a value of the wrong type as a fallback
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
c8ea357fa7
|
Answer architecture round 1: 2 🔴, 5 🟡; nesting counts the JSON fallback alone, one mark attrs read and spell, one mark table, a malformed mark is unsupported-node-shape, the old colwidth names the comma list, README and notes name the attrs fallback
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
d5b9356a29
|
Record the marks and colwidth spellings in the spec, decisions, changelog and migration guide
|
2026-10-14 10:48:12 +02:00 |
|
lilleman
|
5f1c64b371
|
Answer prose round 1: 0 🔴, 7 🟡; the guarantee splits per reader, the spec's portable sentence follows the named errors, item 112 names rows holding no pipe
|
2026-10-14 01:17:39 +02:00 |
|
lilleman
|
ec9492635a
|
Read GFM's pipe table without leading pipes and with alignment colons in portableMarkdownToAdf
|
2026-10-14 01:17:39 +02:00 |
|
lilleman
|
6152808194
|
Answer prose round 1: 0 🔴, 2 🟡; the slot's rule joins the node-tables bullet, the remedies offer the space alike, the message says lines
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
5cd07cafec
|
Answer architecture round 1: 0 🔴, 2 🟡; the slot's line ending is a value the slot does not take, and its message offers the space again
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
06df26727a
|
Fold unspellable-whitespace into unsupported-node-shape
|
2026-10-14 00:26:19 +02:00 |
|
lilleman
|
eff957fbbe
|
Answer CodeRabbit's review: 0 🔴, 1 🟡; only a catchable out-of-memory throw is engine-limit, and isolation from heap exhaustion takes a separate process, not a worker
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
667360f6e6
|
Answer prose round 1: 0 🔴, 9 🟡; the retry paragraph, the guarantees, the changelog and the code-list entry each say one thing once, the engine-limit message names what it covers, the persona line excepts engine-limit by the maintainer's call, and the error row's split is filed as item 111
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
d13a17565b
|
Answer architecture round 3: 0 🔴, 0 🟡; an out-of-memory throw is engine-limit whatever the engine ran short of, the ruling reads same
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
563133f3ee
|
Answer architecture round 1: 2 🔴, 5 🟡; readableBlock alone fills and reads the spelling memo, the escaper's steps hand on what they claim rather than write a shared buffer, engine-limit names only the throws an engine returns, and the docs agree on it
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
d90898c6ec
|
Return the new code engine-limit where the engine runs short of memory or passes its longest array, so unsupported-node-shape stays deterministic
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
f7cbabdf38
|
Answer product-owner round 1: the changelog states the memory a character costs, not a heap that varies by machine, and what the reader returns now
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
03b4ab2e44
|
Spell a line in memory linear in its length, so a paragraph up to V8's longest string converts within Node's default heap
|
2026-10-13 20:10:29 +02:00 |
|
lilleman
|
7bc69355c3
|
Answer prose round 1: the refusal messages name what passed the bound, the decisions read one idea a sentence, and the changelog gives the readers' fix its own bullet
|
2026-10-13 01:30:12 +02:00 |
|
lilleman
|
4657796d4d
|
Answer stability round 1: the guard's comment holds at both its call sites, and a giving-way list's items keep the list's path
|
2026-10-13 01:30:12 +02:00 |
|
lilleman
|
3414c8690a
|
Answer architecture round 2: every builder joins its pieces through one bounded join, the readers take the engine guard, every refusal stands at the document's path, and a portable list's refusal names its own place
|
2026-10-13 01:30:12 +02:00 |
|
lilleman
|
e3aa790ec8
|
Refuse markdown past V8's longest string on every engine, before building it
|
2026-10-13 01:30:12 +02:00 |
|
lilleman
|
62d80a69b7
|
Answer prose round 1: the README says which refusal differs between engines, items 106 and 107 read one idea a sentence, and two test titles and a comment read on one pass
|
2026-10-11 21:05:07 +02:00 |
|
lilleman
|
5e05fa6f30
|
Answer stability round 2: the advice names the array limit, the guard's test names both, and the decision rewraps
|
2026-10-11 21:05:07 +02:00 |
|
lilleman
|
80b4e0a9b7
|
Answer stability round 1: the docs name V8's array limit in one text node, a test pins Invalid array length, and item 106 takes the readers' RangeError and JavaScriptCore's Out of memory
|
2026-10-11 21:05:07 +02:00 |
|
lilleman
|
a9331b4125
|
Return a result where a conversion's text would pass the engine's longest string
|
2026-10-11 21:05:07 +02:00 |
|
lilleman
|
1b39f17ac0
|
Answer prose round 1: the spec names each title and destination, the writing verdict is its own decision citing item 100, items 99 and 101 state what holds, and the migration and changelog rows say what they replace
|
2026-10-11 13:31:18 +02:00 |
|
lilleman
|
5fa53cb795
|
Answer stability round 1: tryImage drops an exit the comparison already takes, the README and changelog scope the linked image, and item 101 files the refusal naming its spelling
|
2026-10-11 13:31:18 +02:00 |
|
lilleman
|
5f2c5083e9
|
Answer architecture round 1: the portable writer builds the linked image through externalMedia, the properties generate the image shapes, linkDefinition sits beside linkMark, the changelog drops a refusal no release met, and items 99 and 100 file the inline linked image and the caption reading
|
2026-10-11 13:31:18 +02:00 |
|
lilleman
|
580bc862f2
|
Write an external image a link marks as [](href) in both writers
|
2026-10-11 13:31:18 +02:00 |
|
lilleman
|
cea9137495
|
Answer prose round 1: the comments and test name say what ends a list, the README says because, the changelog leads with the rename and gives the definition's trigger, and items 56 and 98 state their claims plainly
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
419bb10324
|
Answer product-owner round 1: the migration row names the trigger and how to keep one list, the changelog groups the list entries and labels its fixes, and the README's second group says it has other reasons
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
7d00b11b2c
|
Answer architecture round 1: closeLeaf records the block definitions end beside the blocks it pushes, openedList's comment names the exception, the README drops its counts, the changelog puts other changes last, and item 98 files the blank-line re-scan
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
fa7f4ef987
|
Read two lists a link reference definition parts as two lists, and put the changelog's breaking entries first
|
2026-10-10 13:20:05 +02:00 |
|
lilleman
|
c6017526ac
|
Answer auto-reviewer round 1: the changelog line says a long run took seconds before and takes milliseconds now
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
c0d93e4db3
|
Answer product-owner round 1: the changelog line says what a long run cost before, and item 33 states its cost at this commit
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
b953be2ed4
|
File item 95 for the read-back, and note the linear escape in the changelog
|
2026-10-09 19:17:20 +02:00 |
|
lilleman
|
167bf1ff9b
|
Answer prose round 1: the decision says right after and keeps only its reason, the README counts the link-definition exception, and the comments and spec say which list alternates
|
2026-10-09 15:39:13 +02:00 |
|
lilleman
|
a0166982b1
|
Answer product-owner round 1: the README states the alternate marker and the * escape, and the changelog names which writer dropped ::listBreak
|
2026-10-09 15:39:13 +02:00 |
|
lilleman
|
40580e6948
|
Read a list whose bullet or ordered delimiter changes as two lists, and alternate the marker between adjacent lists in place of !adf:listBreak
|
2026-10-09 15:39:13 +02:00 |
|
lilleman
|
cd6cb8bece
|
Answer prose round 1: a task item keeps the task lists right after its paragraphs nested, and the README, changelog, decision, comment, item 49 and a test title say it plainly
|
2026-10-09 14:37:06 +02:00 |
|
lilleman
|
0c56a479bb
|
Answer product-owner round 3: the changelog keeps nested only a task list before the block that splits the item
|
2026-10-09 14:37:06 +02:00 |
|
lilleman
|
217ab190f3
|
Answer product-owner round 2: the README's read-back cell and the changelog keep a nested task list nested, and item 93 ships in 0.2.0, where the portable reader first ships
|
2026-10-09 14:37:06 +02:00 |
|