mirror of
https://github.com/larvit/adf-codec.git
synced 2026-11-20 15:15:44 +01:00
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
This commit is contained in:
+4
-3
@@ -92,9 +92,10 @@
|
|||||||
- Fix the markdown readers past the longest string or array the JavaScript engine builds: they
|
- Fix the markdown readers past the longest string or array the JavaScript engine builds: they
|
||||||
return `unsupported-node-shape` where they threw.
|
return `unsupported-node-shape` where they threw.
|
||||||
- Fix a paragraph of tens of millions of characters: `adfToLosslessMarkdown` and
|
- Fix a paragraph of tens of millions of characters: `adfToLosslessMarkdown` and
|
||||||
`adfToPortableMarkdown` write one up to 536870888 characters within Node's default heap, where 80
|
`adfToPortableMarkdown` write it in a few bytes of memory a character beyond the document and its
|
||||||
million characters ran out of memory and 20 million `*` threw `RangeError`. `losslessMarkdownToAdf`
|
markdown, where they took about 50, so 80 million characters ran Node's default heap out of memory
|
||||||
no longer throws on such a paragraph inside a directive.
|
and 20 million `*` threw `RangeError`. `losslessMarkdownToAdf` returns a result for such a
|
||||||
|
paragraph inside a directive, where it threw `RangeError`.
|
||||||
- Fix deeply nested compact JSON in an `adf:` fence: `losslessMarkdownToAdf` refuses it as
|
- Fix deeply nested compact JSON in an `adf:` fence: `losslessMarkdownToAdf` refuses it as
|
||||||
`unsupported-node-shape`, as it refuses any compact JSON there, where about a megabyte of it threw.
|
`unsupported-node-shape`, as it refuses any compact JSON there, where about a megabyte of it threw.
|
||||||
- Add `adfToPortableMarkdown` and `portableMarkdownToAdf`, a lossy pair converting ADF to and from
|
- Add `adfToPortableMarkdown` and `portableMarkdownToAdf`, a lossy pair converting ADF to and from
|
||||||
|
|||||||
Reference in New Issue
Block a user