larvit/adf-codec
3
0
Fork 0
mirror of https://github.com/larvit/adf-codec.git synced 2026-11-12 11:48:29 +01:00
Code Activity

Answer prose round 1: 2 🔴, 2 🟡 (0 misread); say the breaking change is accepted and drop the confirm step

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-11-04 21:07:32 +01:00
committed by Lillem4n
parent 8bc6546c78
commit dbaa6823aa
2 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decisions.md
+4 -3
View File
@@ -775,9 +775,10 @@ and no spelling holds; nesting depth; output length; what a portable line can sp
reader's refusal of markdown or HTML it cannot read. A schema refusal a converter gains later is
made in the first step too.
The maintainer's reason (2026-11-04): the library's behaviour in and out stays as it is; the
checks run at the first step and answer the same whatever format the ADF converts to. The rule adds
no refusal for a shape no writer refuses today.
The aim is the same behaviour in and out, with the checks run at the first step and alike in every
format. Each shape the first step refuses is one some writer refuses today. The change this
makes is that every writer, and every carry reader, now refuses it: the maintainer accepts that
breaking change, since the library is not on 1.x.
The earlier entries premised that the site a document is saved to validates the rest. A
hand-built document has not reached the site yet, and the viewer/editor persona relies on a
todo.md
+3 -5
View File
@@ -124,11 +124,9 @@ reading; `MIGRATION.md` says to convert it once with the last version that reads
`CHANGELOG.md` and `MIGRATION.md`. Search the writers for any other refusal of a shape the schema
forbids, and `carriedNode` for one the readers still build.
The maintainer wants the behaviour in and out unchanged, with the checks alike in every format. The
first step cannot tell which node one format's carry holds, so a shape that one writer refuses now
is refused in all, a carried node included. That is the one change of behaviour: confirm it with
the maintainer before the chunk ships, and file a `question` item if they want the carried case
kept as it is.
The aim is the same behaviour in and out, with the checks alike in every format. The breaking
change above is what "alike" costs: `refusedShape` takes no format, so it cannot spare a node that
only one writer carries. The maintainer accepted it (2026-11-04); the item adds no other refusal.
Stays where it is: a node holding one mark type twice (the schema allows it, no spelling holds it),
nesting depth, output length, a portable task list holding what no list item spells, and a