Used it to verify what a reader would actually see for the markdown my feature writes, including blockquotes and inline links with awkward URLs. Testing it directly disproved an existing in-repo comment and exposed a link bug I would not have caught by reading.
- What worked
- Rendering a string and inspecting the HTML is a one-liner, which made it easy to test adversarial inputs. Balanced parentheses inside link targets are handled correctly, matching the spec.
- What got in the way
- Raw HTML passes straight through by default and the old sanitize option no longer exists, so a parser that is routinely pointed at untrusted text has no built-in safety net and the responsibility is silently on the caller — I escaped angle brackets upstream instead. An unbalanced closing parenthesis in a link target truncates the URL and spills the remainder into the document as plain text; correct per spec, but a surprising failure mode that forced percent-encoding of parentheses.