Skip to content

163_public-markdown-library.md

Latest commit

 

History

History
106 lines (94 loc) · 3.1 KB

163_public-markdown-library.md

File metadata and controls

106 lines (94 loc) · 3.1 KB
Raw
id 163
title Extract mdsmith Markdown parse/produce as a public Go library
status 🔲
summary Expose mdsmith's Markdown parsing and a canonical producer as a stable public Go package so the linter core and release tooling share one implementation instead of separate goldmark configs.
model
depends-on

Extract mdsmith Markdown parse/produce as a public Go library

Goal

Give mdsmith one importable Markdown surface. It covers parse and produce. Callers stop reinventing it. They stop coupling to the linter core.

Context

This is option C deferred from PR #291. The sync-docs work there needed to parse a doc and emit Markdown. The three options were:

  1. Raw goldmark inside internal/release (chosen, interim).
  2. Reuse the linter parser — rejected: it couples release tooling to the linter core and the architecture hub keeps that boundary.
  3. A public library — best end state, but a separate initiative, captured here.

Two facts make C real work, not a move:

  • There is no producer to expose. mdsmith fix is edit-based: it applies per-rule segment edits, not an AST → Markdown render. A reusable producer is net-new design.
  • Everything sits under internal/. A public package is a semver and documentation commitment, and the parser config in internal/rules/markdownflavor imports internal/lint, so the parse path must be untangled from linter concerns first.

When this lands, the public package replaces the interim goldmark config in internal/release/syncdocs.go. Behavior does not change.

Tasks

  1. Design the public API: a parse entry that returns the goldmark AST plus front matter, and a producer entry that surgically edits source spans (the model sync-docs already relies on). Decide the package path (pkg/markdown vs a top-level module).
  2. Untangle the parser config from internal/lint so parsing has no rule/config/diagnostic dependency.
  3. Build the producer: a documented, tested surgical-splice + render path that does not fight mdsmith fix output.
  4. Migrate internal/release off its local goldmark config onto the public package; assert identical sync-docs output.
  5. Migrate the linter core to the same package so there is a single parser config in the tree.
  6. Add API docs and a semver policy entry under docs/development.

Acceptance Criteria

  • A public package exposes parse + produce with a documented, stable API.
  • No public parse path imports the linter core (internal/lint).
  • sync-docs and the linter both consume the public package; only one goldmark config remains in the tree.
  • sync-docs output is byte-identical before and after the migration.
  • All tests pass: go test ./....
  • go tool golangci-lint run reports no issues.
  • mdsmith check . passes.