Skip to content

Improve markdown fidelity in appendMarkdownToGoogleDoc#44

Merged
a-bonus merged 1 commit intoa-bonus:mainfrom
wulymammoth:dwu/markdown-fidelity-upgrades
Feb 11, 2026
Merged

Improve markdown fidelity in appendMarkdownToGoogleDoc#44
a-bonus merged 1 commit intoa-bonus:mainfrom
wulymammoth:dwu/markdown-fidelity-upgrades

Conversation

@wulymammoth
Copy link
Copy Markdown
Contributor

@wulymammoth wulymammoth commented Feb 11, 2026

Summary

This PR improves markdown-to-Google-Docs fidelity used by appendMarkdownToGoogleDoc and replaceDocumentWithMarkdown by adding support for patterns that previously degraded formatting.

What Changed

  • Add inline-code styling (monospace + code-like colors).
  • Add fenced/code-block rendering and code styling.
  • Preserve nested list levels via leading-tab indentation.
  • Convert markdown task lists ([x] / [ ]) to Google Docs checkbox bullets.
  • Prevent list bullet ranges from bleeding into following headings.
  • Apply list bullet requests bottom-up to avoid index-shift failures.
  • Add regression tests for the above behavior.

Validation

  • Ran: node --test tests/markdown.test.js
  • Result: 22 passed, 0 failed.

Before / After Evidence (Public-Safe Fixture)

Used a synthetic markdown fixture (no internal content).

  • Before (origin/main converter):
    • checkbox bullets: not generated
    • monospace code style requests: 0
Screenshot 2026-02-10 at 10 30 41 PM
  • After (this branch):
    • checkbox bullets: generated
    • monospace code style requests: 3
Screenshot 2026-02-10 at 10 30 48 PM

@wulymammoth
Copy link
Copy Markdown
Contributor Author

@cyberkni thank you for the work you did on #40. feel free to review this code and the enhancement i'm making.

@a-bonus
Copy link
Copy Markdown
Owner

a-bonus commented Feb 11, 2026

Amazing, thank you 🙏🙏

@a-bonus a-bonus merged commit c8bea3b into a-bonus:main Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants